From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Jim Meyering" <jim@meyering.net>
Cc: git@vger.kernel.org
Subject: Re: synchronizing incremental git changes to cvs
Date: Sun, 21 May 2006 12:09:19 +1200 [thread overview]
Message-ID: <46a038f90605201709n3a840fd9n7e85a289f49a3c5f@mail.gmail.com> (raw)
In-Reply-To: <87mzdcjqey.fsf@rho.meyering.net>
On 5/21/06, Jim Meyering <jim@meyering.net> wrote:
> Can anyone point me at code to mirror a git repository to cvs?
Ive thought a couple of times about writing an exporter that would
replay things into a true CVS repo, but it's truly not worth it. We've
already got git-cvsserver that does all that -- better for me to focus
on that codebase.
> I've experimented with git-cvsexportcommit, and found a few bugs (it
> couldn't handle simple things, like adding a file in a new directory --
> fixed that, along with a few other minor problems), adding an empty file
> in git still gets a patch application error on the cvs side, but I can
> live with that for now. More seriously, making a change on a git branch
> mistakenly tries to apply the delta on the cvs trunk.
cvsexportcommit is clearly for manual usage, not for automagic usage.
It is a bit rough, (and I'd like to see your patches to it!) but it
wants to be driven by a smarter script to, for instance, know what
branch you want things in.
> Why am I interested? I want to switch the development of GNU coreutils
> from cvs to git. I would also like to continue making the repository
> available via cvs, for the sake of continuity. At worst, I can always
> cut the CVS cord, but that's a last resort.
git-cvsserver is the word. It currently tracks the git repo itself
pretty well (perfectly, AFAICS) and it also tracks a git tree that is
actually imported daily from CVS -- doing
CVSrepo ->cvsimport -> GIT -> cvsserver -> CVS checkout
git-cvsserver works great for anon cvs access (does pserver) and
TortoiseCVS and cli cvs work great with it. Eclipse works well, but it
has been quite hard to get 'right'. Optionally, it can support users
with commit rights via ssh. It does track git 'heads' but they don't
show up as branches, they show up as different modules. So you to get
a checkout of the master branch, you do:
cvs -d pserver:anonymouys@foo.com:/var/foo.git co master
hope that helps!
martin
next prev parent reply other threads:[~2006-05-21 0:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-20 22:13 synchronizing incremental git changes to cvs Jim Meyering
2006-05-20 23:05 ` Johannes Schindelin
2006-05-21 13:40 ` Jim Meyering
2006-05-22 16:29 ` Pavel Roskin
2006-05-22 17:05 ` Jakub Narebski
2006-05-21 0:09 ` Martin Langhoff [this message]
2006-05-21 16:37 ` Jim Meyering
2006-05-21 18:21 ` Junio C Hamano
2006-05-21 21:31 ` Jim Meyering
2006-05-21 21:35 ` don't accept bogus N in `HEAD~N' Jim Meyering
2006-05-21 21:42 ` Jakub Narebski
2006-05-22 7:38 ` Jim Meyering
2006-05-22 8:16 ` Junio C Hamano
2006-05-22 8:25 ` Junio C Hamano
2006-05-22 6:57 ` avoid atoi, when possible; int overflow -> heap corruption Jim Meyering
2006-05-22 13:16 ` Morten Welinder
2006-05-22 13:31 ` Jim Meyering
2006-05-22 13:37 ` Jeff King
2006-05-22 13:54 ` Morten Welinder
2006-05-22 10:27 ` detect write failure, even for stdout Jim Meyering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46a038f90605201709n3a840fd9n7e85a289f49a3c5f@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).