path: root/Documentation/git-cvsimport.txt
diff options
authorMatthew Ogilvie <>2008-07-05 04:43:41 (GMT)
committerJunio C Hamano <>2008-07-06 00:42:16 (GMT)
commita41a32bf1ce74f3be5c1ab398db1a93b89e6a99e (patch)
treebe09b31f54da0425dfa341b7bdd3a737697b39c7 /Documentation/git-cvsimport.txt
parent2b2da6846370978123935258890a059167dc73bd (diff)
Documentation cvs: Clarify when a bare repository is needed
New users sometimes import a project and then immediately try to use the imported repository as a central shared repository. This provides pointers about setting up a bare repository for that in the parts of the documentation dealing with CVS migration. Signed-off-by: Matthew Ogilvie <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-cvsimport.txt')
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt
index 2f9b35f..93b7d2d 100644
--- a/Documentation/git-cvsimport.txt
+++ b/Documentation/git-cvsimport.txt
@@ -31,6 +31,12 @@ 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.
+If you intend to set up a shared public repository that all developers can
+read/write, or if you want to use linkgit:git-cvsserver[1], then you
+probably want to make a bare clone of the imported repository,
+and use the clone as the shared repository.
+See linkgit:gitcvs-migration[7].