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

Re: [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats

From
Eric S. Raymond <esr@thyrsus.com>
Date
Sep 22, 2016, 13:15 UTC
Message-ID
<20160922131526.GB6320@thyrsus.com>
In-Reply-To
<20160922072628.rs47hfiowtobw46s@sigill.intra.peff.net>
Jeff King <peff@peff.net>:
> Back when this guide was written, cvsimport was the only
> game in town. These days it is probably not the best option.

It is absolutely not. As I have tried to point out here before, it is *severely* broken in its processing of branchy CVS repositories.

Nobody wanted to hear that, but it's still true. Recommending it is irresponsible.

-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Previous: Jeff KingNext: Jeff King
Message 5 of 9 in “update git cvs import documentation”
  1. 0/3 update git cvs import documentationJeff King, Sep 22, 2016
  2. 1/3 docs/cvsimport: prefer cvs-fast-export to parsecvsJeff King, Sep 22, 2016
  3. 2/3 docs/cvs-migration: update link to cvsps homepageJeff King, Sep 22, 2016
  4. 3/3 docs/cvs-migration: mention cvsimport caveatsJeff King, Sep 22, 2016
  5. Eric S. RaymondSep 22, 2016
  6. Jeff KingSep 23, 2016
  7. Eric S. RaymondSep 28, 2016
  8. Jeff KingSep 28, 2016
  9. Junio C HamanoSep 28, 2016

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.