Switching from CVS to GIT

[Paul Smith]

Hi all;

I'm considering switching from CVS to another form of SCM.  Currently,
Savannah supports (in addition to CVS) GNU arch and GIT.  If SVN were
supported I'd probably go for that, because (a) it has great support for
alternative OSs like Windows, etc.; and (b) GNU make development is
currently straightforward enough that the advanced features of GIT
(advanced merging and peer-to-peer development) aren't critical.
However, SVN is not an option and I would like some more advanced SCM
capabilities such as moving/renaming files (I've been putting off some
code cleanups waiting for this).

It seems like GIT is where the mindshare is these days, plus a number of
the other autotools projects have already migrated (or are in the middle
of migrating) to GIT, so that's what I'd go with.  As with the other
projects, we'll maintain a read-only CVS mirror of the main GIT archive
at least for the time being so people can use that to obtain code, the
same way they do today.  Still, it would be better if people had more
direct access; I'd be happy to delegate support for Windows (MINGW,
Cygwin, etc.) and pull those from other GIT repositories if that seems
reasonable.

I don't really know what the current state-of-the-art is WRT GIT on
non-POSIX systems, so... please give me your opinions on this change.


Cheers!

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <address@hidden>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.mad-scientist.us
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist