[PATCH 3/3] docs/cvs-migration: mention cvsimport caveats
- From
Jeff King <peff@peff.net>
- Date
- Sep 22, 2016, 07:26 UTC
- Message-ID
- <20160922072628.rs47hfiowtobw46s@sigill.intra.peff.net>
- 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