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

Re: Problem with git-cvsimport

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Oct 30, 2007, 21:44 UTC
Message-ID
<200710302244.50034.robin.rosenberg.lists@dewire.com>
In-Reply-To
<170fa0d20710301306o6b3798f9k72615eb811d871f2@mail.gmail.com>
tisdag 30 oktober 2007 skrev Mike Snitzer:
Show 17 quoted lines
> On 10/10/07, Eyvind Bernhardsen <eyvind-git-list@orakel.ntnu.no> wrote:
> ...
> >
> > Thanks for making cvs2svn the best CVS-to-git conversion tool :)  Now
> > if it would only support incremental importing...
> 
> Michael,
> 
> I second this question: is there any chance incremental importing will
> be implemented in cvs2svn?
> 
> I've not used cvs2svn much and when I did it was for svn not git; but
> given that git-cvsimport is known to mess up your git repo (as Eyvind
> pointed out earlier) there doesn't appear to be any reliable tools to
> allow for incrementally importing from cvs to git.
> 
> Are others using a tool for reliably importing from cvs to git?

I use fromcvs which is *very* fast, and quite memory conservative compared to the others and seems reliable so far (six months). It probably breaks on exotic variants of branches though, but I don't have those / don't care about them.

Do not push into the same repo fromcvs works on. I don't understand why, but I pushed once and *poof* the conversion went bad.

Drawbacks, more dependencies and access to the rcs files is required and tags are not converted.

-- robin
Previous: Mike SnitzerNext: Aidan Van Dyk
Message 9 of 11 in “Problem with git-cvsimport”
  1. Thomas PaschOct 9, 2007
  2. Jan WielemakerOct 9, 2007
  3. Gerald (Jerry) CarterOct 9, 2007
  4. Eyvind BernhardsenOct 9, 2007
  5. Michael HaggertyOct 10, 2007
  6. Eyvind BernhardsenOct 10, 2007
  7. Mike SnitzerOct 30, 2007
  8. Mike SnitzerOct 30, 2007
  9. Robin RosenbergOct 30, 2007
  10. Aidan Van DykOct 31, 2007
  11. Michael HaggertyOct 31, 2007

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.