PATCH] cvsimport: Clarification on the use of -r
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
---
Documentation/git-cvsimport.txt | 10 +++++++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt
index 2f9b35f..b873882 100644
--- a/Documentation/git-cvsimport.txt
+++ b/Documentation/git-cvsimport.txt
@@ -28,8 +28,12 @@ You should *never* do any work of your own on the branches that are
created by git-cvsimport. By default initial import will create and populate a
"master" branch from the CVS repository's main branch which you're free
to work with; after that, you need to 'git merge' incremental imports, or
-any CVS branches, yourself. It is advisable to specify a named remote via
--r to separate and protect the incoming branches.
+any CVS branches, yourself.
+
+It is advisable to specify a named remote via -r to separate and protect
+the incoming branches if you intend to do your work in the same repository. If
+you want to have a cvs import-only repostory which you clone to your work
+repository, then do not use the -r option.
OPTIONS
@@ -56,7 +60,7 @@ OPTIONS
-r <remote>::
The git remote to import this CVS repository into.
Moves all CVS branches into remotes/<remote>/<branch>
- akin to the git-clone --use-separate-remote option.
+ akin what git clone does when cloning a repository.
-o <branch-for-HEAD>::
When no remote is specified (via -r) the 'HEAD' branch
--
1.5.5.1.178.g1f811
Robin Rosenberg <robin.rosenberg.lists@dewire.com>