git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Chanters <david.chanters@googlemail.com>
To: git@vger.kernel.org
Cc: David Chanters <david.chanters@googlemail.com>
Subject: CVS <--> GIT workflow...
Date: Wed, 1 Jul 2009 19:32:33 +0100	[thread overview]
Message-ID: <ac3d41850907011132q8e19b37ofa10813258a97555@mail.gmail.com> (raw)

Hi all,

[ Please Cc me, as I am not subscribed to the list. ]

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.  :)

Thanks, in advance,

David

             reply	other threads:[~2009-07-01 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 18:32 David Chanters [this message]
2009-07-01 19:24 ` CVS <--> GIT workflow John Tapsell
2009-07-01 19:29   ` David Chanters
2009-07-01 20:00 ` Jakub Narebski
2009-07-01 21:25   ` David Chanters
2009-07-02 12:01     ` Nick Woolley

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=ac3d41850907011132q8e19b37ofa10813258a97555@mail.gmail.com \
    --to=david.chanters@googlemail.com \
    --cc=git@vger.kernel.org \
    /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).