From: Jakub Narebski <jnareb@gmail.com>
To: Jvsrvcs <jvsrvcs@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git: CVS to Git import
Date: Fri, 11 Nov 2011 15:43:47 -0800 (PST) [thread overview]
Message-ID: <m3obwimdi1.fsf@localhost.localdomain> (raw)
In-Reply-To: <1321053453892-6987037.post@n2.nabble.com>
Jvsrvcs <jvsrvcs@gmail.com> writes:
> Git: CVS to Git import
>
> We are moving from CVS to Git and want to know if anyone has had any
> experience there doing this and could share do's / dont's, best practices
> when doing the initial import.
>
> Also are there any known problems/bugs with the cvs to git import with
> regards to CVS history?
I think that Eric S Raymond "DVCS Migration Guide"
http://www.catb.org/esr/dvcs-migration-guide.html
and reposurgeon tool (to clean up conversion artifacts)
http://www.catb.org/esr/reposurgeon/
might help.
--
Jakub Narębski
next prev parent reply other threads:[~2011-11-11 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 23:17 Git: CVS to Git import Jvsrvcs
2011-11-11 23:43 ` Jakub Narebski [this message]
2011-11-12 0:24 ` Jonathan Nieder
2011-11-14 2:44 ` Matthew Ogilvie
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=m3obwimdi1.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jvsrvcs@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).