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

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

From
Jeff King <peff@peff.net>
Date
Sep 28, 2016, 06:41 UTC
Message-ID
<20160928064149.m3j5z5tr4zopet5h@sigill.intra.peff.net>
In-Reply-To
<20160928001108.GA9120@thyrsus.com>
On Tue, Sep 27, 2016 at 08:11:08PM -0400, Eric S. Raymond wrote:
Show 6 quoted lines
> Jeff King <peff@peff.net>:
> >               I am not qualified to write on the current state of
> > the art in CVS importing.
> 
> I *am* qualified; cvs-fast-export has had a lot of work put into it by
> myself and others over the last five years.

I, for one, would be fine if you wanted to send a patch updating Documentation/gitcvs-migration.txt to describe cvs-fast-export rather than cvsimport. I think it would probably even be fine if it mostly just pointed to an existing guide and said "use this".

-Peff
Previous: Eric S. RaymondNext: Junio C Hamano
Message 8 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.