hi john or whoever:

would you mind removing "CsoundX" from the frontends folder in the repository?
( i assume i don't have permission to do this? )

i am currently revising it (replacing a bunch of old technologies)
and as it is now it doesn't quite work.  i think it would be best to remove it and i can
add the new version (with a new name to avoid conflict with the ~other~ CsoundX!)

look forward to gitting acquainted with git! ( i think )

thanks,
matt

On Feb 14, 2011, at 7:08 AM, John ff wrote:

> The overwhelming vote has been for git.  A discussion with Felipe has
> clarified my ideas, so the sooner we move the better.
> 
> The stages are
> 
> 1: Everyone commits to CVS anything the need to
> 
> 2: Write access to CVS is (temporally) removed
> 
> 3: Code (at least csound5 and manuals) moved to git
> 
> 4: Write access to git opened up and CVS access rationalised
> 
> 5: Distribution of basic instructions (I know there are help resources
> but some assistance from git users to the rest of us would be nice)
> 
> 
> Is there anything missing from that schedule?
> When should we do it?  I am hoping that the process should be of the
> order of hours rather than days -- or even minutes.
> Any offers to write a dummies guide to using git?
> 
> I have looked at the preservation of the history and while not perfect
> seems adequate.
> 
> ==John ffitch
> 
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net