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

Re: cvsimport: trying to convert freebsd cvs to git

From
David Soria Parra <sn_@gmx.net>
Date
Dec 23, 2007, 12:06 UTC
Message-ID
<fklivc$cio$1@ger.gmane.org>
In-Reply-To
<pan.2007.12.23.01.47.29@progsoc.org>
> If you have access to the raw ",v" files as you do, I would suggest you 
> try out parsecvs. It will not do incremental imports but will you a good 
> idea of how you can expect the converted repository to behave / act.

ParseCVS works out fine with the PHP repository for us while cvsimport has some problems with branches. For me it looks like doing parsecvs on an existing repository tries to check all ,v files but in fact producing a more or less incremental update.

If you try to use parsecvs make sure that your branchname doesnot contain / or ~ as this will cause an error on parsecvs. If you need it, we have a simple patch for that with a small workaround on that.

Previous: Anand KumriaNext: Jeff King
Message 3 of 9 in “cvsimport: trying to convert freebsd cvs to git”
  1. Miklos VajnaDec 22, 2007
  2. Anand KumriaDec 23, 2007
  3. David Soria ParraDec 23, 2007
  4. Jeff KingDec 23, 2007
  5. Martin LanghoffDec 23, 2007
  6. Jeff KingDec 24, 2007
  7. cvsimport: die on cvsps errorsJeff King, Dec 24, 2007
  8. Martin LanghoffDec 24, 2007
  9. Miklos VajnaDec 24, 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.