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

[PATCH 1/3] docs/cvsimport: prefer cvs-fast-export to parsecvs

From
Jeff King <peff@peff.net>
Date
Sep 22, 2016, 07:25 UTC
Message-ID
<20160922072527.xy3q227ygs6orhfj@sigill.intra.peff.net>
In-Reply-To
<20160922072350.ivjrfuedodd2rezn@sigill.intra.peff.net>

parsecvs maintenance was taken over by ESR, and the name changed to cvs-fast-export as it learned to support that output format. Let's point to cvs-fast-export, as it should have additional bug-fixes and be more convenient to use.

Signed-off-by: Jeff King <peff@peff.net>
---
No opinion on how this compares to cvs2git these days, so I made the
minimal change here. Anyone may feel free to debate it, but kindly
remove me from the Cc of any flamewars. :)
 Documentation/git-cvsimport.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt
index 41207a2..de1ebed 100644
--- a/Documentation/git-cvsimport.txt
+++ b/Documentation/git-cvsimport.txt
@@ -22,7 +22,7 @@ DESCRIPTION
 deprecated; it does not work with cvsps version 3 and later.  If you are
 performing a one-shot import of a CVS repository consider using
 http://cvs2svn.tigris.org/cvs2git.html[cvs2git] or
-https://github.com/BartMassey/parsecvs[parsecvs].
+http://www.catb.org/esr/cvs-fast-export/[cvs-fast-export].
 
 Imports a CVS repository into Git. It will either create a new
 repository, or incrementally import into an existing one.
-- 
2.10.0.482.gae5a597
Previous: Jeff KingNext: Jeff King
Message 2 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.