git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: esr@thyrsus.com
Subject: [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats
Date: Thu, 22 Sep 2016 03:26:28 -0400	[thread overview]
Message-ID: <20160922072628.rs47hfiowtobw46s@sigill.intra.peff.net> (raw)
In-Reply-To: <20160922072350.ivjrfuedodd2rezn@sigill.intra.peff.net>

Back when this guide was written, cvsimport was the only
game in town. These days it is probably not the best option.
Rather than go into details, let's point people to the note
at the top of cvsimport which gives other options.

Signed-off-by: Jeff King <peff@peff.net>
---
 Documentation/gitcvs-migration.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/gitcvs-migration.txt b/Documentation/gitcvs-migration.txt
index faee5c2..4c6143c 100644
--- a/Documentation/gitcvs-migration.txt
+++ b/Documentation/gitcvs-migration.txt
@@ -116,6 +116,10 @@ they create are writable and searchable by other group members.
 Importing a CVS archive
 -----------------------
 
+NOTE: These instructions use the `git-cvsimport` script which ships with
+git, but other importers may provide better results. See the note in
+linkgit:git-cvsimport[1] for other options.
+
 First, install version 2.1 or higher of cvsps from
 https://github.com/andreyvit/cvsps[https://github.com/andreyvit/cvsps] and make
 sure it is in your path.  Then cd to a checked out CVS working directory
-- 
2.10.0.482.gae5a597

  parent reply	other threads:[~2016-09-22  7:27 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 ` [PATCH 1/3] docs/cvsimport: prefer cvs-fast-export to parsecvs Jeff King
2016-09-22  7:26 ` [PATCH 2/3] docs/cvs-migration: update link to cvsps homepage Jeff King
2016-09-22  7:26 ` Jeff King [this message]
2016-09-22 13:15   ` [PATCH 3/3] docs/cvs-migration: mention cvsimport caveats 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=20160922072628.rs47hfiowtobw46s@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).