From 106b672adee17391e80c34913c8383e6b426b466 Mon Sep 17 00:00:00 2001 From: Jeff King Date: Thu, 22 Sep 2016 03:26:28 -0400 Subject: docs/cvs-migration: mention cvsimport caveats 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 Signed-off-by: Junio C Hamano --- Documentation/gitcvs-migration.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/gitcvs-migration.txt b/Documentation/gitcvs-migration.txt index faee5c21d..4c6143c51 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 -- cgit v1.2.1