All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Towards CVS code-exchange and gateways
Date: Tue, 25 Oct 2005 17:25:00 -0700	[thread overview]
Message-ID: <7vr7a9azvn.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <46a038f90510251357l23886747s8024a4326ad4e392@mail.gmail.com> (Martin Langhoff's message of "Wed, 26 Oct 2005 09:57:14 +1300")

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.

  reply	other threads:[~2005-10-26  0:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 20:57 Towards CVS code-exchange and gateways Martin Langhoff
2005-10-26  0:25 ` Junio C Hamano [this message]
2005-10-26  3:35 ` Martin Langhoff
2005-10-26  8:53   ` Petr Baudis
2005-10-26  9:11     ` Martin Langhoff
2005-10-26 20:51       ` Petr Baudis

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=7vr7a9azvn.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=martin.langhoff@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.