transition from CVS to Git?

[Ben Pfaff]

I want to propose transitioning PSPP from CVS to Git, following
the 0.6.0 release, for the following reasons among others:

        * Git supports atomic commits and file and directory
          renaming.

        * Git is fast.  It only uses network access to a remote
          server for initial checkouts and updates and for
          pushing changes to the server.

        * Git has excellent support for branching.  Branching is
          easy enough that you can create a branch for each
          feature you add.  Merging is high-quality enough that
          you can merge back and forth between branches
          repeatedly without the problems that CVS (and
          Subversion?) has with forgetting that some changes have
          already been merged.

        * Git has many useful tools, including a number of useful
          GUI tools.

        * Git is under active development.  New, useful tools are
          being developed for it all the time.

        * Git has good documentation.

Savannah already supports Git.  A number of GNU projects are
already using it there, including Gnulib, Automake, and Autoconf.
(These projects transitioned from CVS also.)

Moving from CVS to Git won't lose any history.  In fact, it makes
the history *easier* to follow, because Git will break the
history into atomic change sets and follow file renames.

So: what do you guys think?
-- 
Ben Pfaff 
http://benpfaff.org