path: root/Documentation/gitcvs-migration.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/gitcvs-migration.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/gitcvs-migration.txt')
1 files changed, 5 insertions, 0 deletions
diff --git a/Documentation/gitcvs-migration.txt b/Documentation/gitcvs-migration.txt
index 1db3f52..0325d67 100644
--- a/Documentation/gitcvs-migration.txt
+++ b/Documentation/gitcvs-migration.txt
@@ -143,6 +143,11 @@ work, you must not modify the imported branches; instead, create new
branches for your own changes, and merge in the imported branches as
+If you want a shared repository, you will need to make a bare clone
+of the imported directory, as described above. Then treat the imported
+directory as another development clone for purposes of merging
+incremental imports.
Advanced Shared Repository Management