From: Junio C Hamano <junkio@cox.net>
Date: Wed, 26 Oct 2005 00:25:00 GMT
Subject: Re: Towards CVS code-exchange and gateways
Message-ID: <7vr7a9azvn.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <46a038f90510251357l23886747s8024a4326ad4e392@mail.gmail.com>

Martin Langhoff <martin.langhoff@gmail.com> writes:

> Is there anyone working on a git -> cvs gateway or similar scripts?

Working on, no, but I was thinking about something like that at
work (today is my non-git day but I use git on top of CVS to
track my private changes in my CVS work tree which is my git
repo there).

I maintain at 'cvs' and 'master' branch (and other git branches)
there, and always 'git-checkout cvs' before doing 'cvs update',
and do 'git-commit' to slurp in the changes to the cvs side.
Then 'git checkout master ; git pull . cvs' to sync the master
side, work on a bit, commit.  Showing what I've done to the CVS
side, currently I do something like this:

      $ git-checkout cvs
      $ git pull . master
      $ git log ORIG_HEAD.. >L
      $ cvs commit -F L

This isn't that bad because I do not care much about how the
development history on the CVS side looks like.  But propagating
each git commit separately to CVS side would be much better, and
what you outlined should work nicely.