diff options
| author |  Matthew Ogilvie <mmogilvi_git@miniinfo.net> | 2008-07-04 22:43:41 -0600 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2008-07-05 17:42:16 -0700 |
| commit | a41a32bf1ce74f3be5c1ab398db1a93b89e6a99e (patch) | |
| tree | be09b31f54da0425dfa341b7bdd3a737697b39c7 /Documentation/git-cvsimport.txt | |
| parent | Documentation: be precise about which date --pretty uses (diff) | |
| download | tgif-a41a32bf1ce74f3be5c1ab398db1a93b89e6a99e.tar.xz | |
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 <mmogilvi_git@miniinfo.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-cvsimport.txt')
| -rw-r--r-- | Documentation/git-cvsimport.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/git-cvsimport.txt b/Documentation/git-cvsimport.txt index 2f9b35f622..93b7d2dc99 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]. + OPTIONS ------- |