From: Reto Glauser <linux@blinkeye.ch>
To: git@vger.kernel.org
Cc: Matthias Urlichs <smurf@smurf.noris.de>, mhagger@tigris.org
Subject: git-cvsimport: missing branches
Date: Wed, 23 Sep 2009 19:35:24 +0200 [thread overview]
Message-ID: <4ABA5C5C.2060207@blinkeye.ch> (raw)
Hello
I need to use CVS with a history of about 20 years (someway back it was
converted from SCCS to CVS). I have to stay in sync with the CVS
repository to import changes from co-workers and to eventually commit
changes back. I do have access to the RCS ',v' files.
So, git-cvsimport is exactly what I was looking for. Except, if I do a
git-cvsimport I have a couple of branches missing, and I don't know why.
I see the branch names from cvsps in the output, but somehow
git-cvsimport skips them anyway. I tried to add a branch manually which
got mit a couple of years of history back, but then it stops anyway.
I used cvs2git from http://cvs2svn.tigris.org which shows me these
missing branches.
So, my questions are:
- Is the problem in cvsps or git-cvsimport or in the CVS history?
- Can I use the cvs2git import as a starting point and later use
git-cvsimport for incrementally update the git repository?
- Can I somehow compare the result of git-cvsimport and cvs2git to see
differences?
- Is there any other feasible workflow to stay in sync with a CVS
repository with a large history while still using git behind the scene?
Any pointers appreciated.
Regards,
Reto
next reply other threads:[~2009-09-23 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 17:35 Reto Glauser [this message]
2009-09-23 19:51 ` git-cvsimport: missing branches Heiko Voigt
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=4ABA5C5C.2060207@blinkeye.ch \
--to=linux@blinkeye.ch \
--cc=git@vger.kernel.org \
--cc=mhagger@tigris.org \
--cc=smurf@smurf.noris.de \
/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).