Re: CVS <--> GIT workflow...

From: Jakub Narebski <jnareb@gmail.com>
Date: Jul 1, 2009, 20:00 UTC
Message-ID: <m3d48kw4uz.fsf@localhost.localdomain>
In-Reply-To: <ac3d41850907011132q8e19b37ofa10813258a97555@mail.gmail.com>

David Chanters <david.chanters@googlemail.com> writes:

Show 18 quoted lines

> I am wondering if there's any best practises/howtos on using CVS and
> Git together.  I have a project which is currently residing in CVS;
> people actively use it to add changes, etc.  Which is fine -- and for
> a variety of reasons we're unable to simply switch away from using CVS
> to Git.
> 
> So... the question is, can I use Git locally to manage all my work in
> -- create topic branches, merge them, etc., and then commit that back
> out to the CVS repository?   Likewise, I would need to keep my Git
> repository in synch with any changes to the CVS repository -- is that
> possible?  Has anyone else done something like this?  What I am
> effectively wanting to do is Git for my entire development on this
> project and just forget it even uses CVS.
> 
> I've read up on git-cvsimport which seems to explain how to convert a
> current CVS repo over to Git -- is that right?  Any information you
> can point me to would be very welcome.  I am not adverse to reading,
> providing it's useful to me.  :)

I think from all CVS importers (git-cvsimport, parsecvs, git mode of cvs2svn aka. cvs2git) only git-cvsimport has incremental mode.

As for exporting to CVS there is git-cvsexportcommit and git-cvsserver (which functions like cvsserver, but conects to git repository; although it has its own limitations).

But you should really hope that your fellow CVS committers use good practice; because it is quite easy to create very messy CVS repository (so that for example it would be hard to extract changesets).

HTH

-- 
Jakub Narebski
Poland
ShadeHawk on #git