From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: esr@thyrsus.com
Subject: [PATCH 1/3] docs/cvsimport: prefer cvs-fast-export to parsecvs
Date: Thu, 22 Sep 2016 03:25:28 -0400 [thread overview]
Message-ID: <20160922072527.xy3q227ygs6orhfj@sigill.intra.peff.net> (raw)
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
next prev parent reply other threads:[~2016-09-22 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 7:23 [PATCH 0/3] update git cvs import documentation Jeff King
2016-09-22 7:25 ` Jeff King [this message]
2016-09-22 7:26 ` [PATCH 2/3] docs/cvs-migration: update link to cvsps homepage Jeff King
2016-09-22 7:26 ` [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats Jeff King
2016-09-22 13:15 ` Eric S. Raymond
2016-09-23 3:56 ` Jeff King
2016-09-28 0:11 ` Eric S. Raymond
2016-09-28 6:41 ` Jeff King
2016-09-28 17:59 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160922072527.xy3q227ygs6orhfj@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).