Switching from CVS to XXX

Hi,

SF is phasing out CVS support (will be read-only at a specific  
deadline). So we will have to switch.

We could now start a bikeshed about which VCS to use, but that  
wouldn't be productive. As such:
  - git has svn support (https://git-scm.com/docs/git-svn)
  - svn has a similar workflow / command structure like cvs
  - svn has nice properties which git doesn't has (like strictly
    incremental revision numbers so that you can directly see if
    X < Y in terms of revision numbers)
  - we are not forced to stay with svn, we can switch from svn to git any time

To me this looks like we can have the good thing of both worlds by  
switching to svn for the official repo, and whoever wants to use git,  
can do so via "git svn". If we should not be happy with the result, we  
can switch to git any time.

So I will try to set some time aside and play around with the  
conversion to SVN.

Consider this to be a early heads-up that "soonish" another VCS repo  
will appear in the lame project. Do not consider it the master (=  
don't use it to build lame and do not make commits to it) until there  
is a message that we officially switch to it (I may delete and redo  
more than once if I'm not happy with the result).

Bye,
Alexander.

-- 
http://www.Leidinger.net [email protected]: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    [email protected]  : PGP 0x8F31830F9F2772BF
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot