From: Michael Haggerty <mhagger@alum.mit.edu>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: files missing after converting a cvs repository to git
Date: Tue, 07 Oct 2008 12:46:30 +0200 [thread overview]
Message-ID: <48EB3E06.70100@alum.mit.edu> (raw)
In-Reply-To: <gcfcrg$ubc$1@ger.gmane.org>
Jakub Narebski wrote:
> Andreas Ericsson wrote:
>
>> cvs2svn is apparently quite good at getting even the weirdest history
>> right. Perhaps you can try that and then running "git svn" on the
>> resulting svn repo?
>
> cvs2svn has git output now (I think it is actually fast-import output)
Correct. See http://cvs2svn.tigris.org/cvs2git.html for more info. I
suggest using the trunk version of cvs2svn for conversions to git.
Please note, however, that cvs2svn can only handle one-time conversions
(i.e., not tracking a live CVS repository incrementally).
Michael
next prev parent reply other threads:[~2008-10-07 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 22:02 files missing after converting a cvs repository to git Adam Mercer
2008-10-07 6:08 ` Andreas Ericsson
2008-10-07 10:15 ` Jakub Narebski
2008-10-07 10:46 ` Michael Haggerty [this message]
2008-10-07 15:58 ` Adam Mercer
2008-10-07 15:55 ` Adam Mercer
2008-10-08 6:16 ` Andreas Ericsson
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=48EB3E06.70100@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=jnareb@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 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).