git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git: CVS to Git import

From
Jakub Narebski <jnareb@gmail.com>
Date
Nov 11, 2011, 23:43 UTC
Message-ID
<m3obwimdi1.fsf@localhost.localdomain>
In-Reply-To
<1321053453892-6987037.post@n2.nabble.com>
Jvsrvcs <jvsrvcs@gmail.com> writes:
Show 8 quoted lines
> 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
Previous: JvsrvcsNext: Jonathan Nieder
Message 2 of 4 in “Git: CVS to Git import”
  1. JvsrvcsNov 11, 2011
  2. Jakub NarebskiNov 11, 2011
  3. Jonathan NiederNov 12, 2011
  4. Matthew OgilvieNov 14, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.