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>

Matthew Ogilvie committed Jul 4, 2008 at 22:43 UTC a41a32bf1ce74f3be5c1ab398db1a93b89e6a99e

3 files changed +14

Documentation/git-cvsimport.txt

@@ -31,6 +31,12 @@ to work with; after that, you need to 'git merge' incremental imports, or

31 any CVS branches, yourself. It is advisable to specify a named remote via

32 -r to separate and protect the incoming branches.

34 +If you intend to set up a shared public repository that all developers can

35 +read/write, or if you want to use linkgit:git-cvsserver[1], then you

36 +probably want to make a bare clone of the imported repository,

37 +and use the clone as the shared repository.

38 +See linkgit:gitcvs-migration[7].

39 +

41 OPTIONS

42 -------

Documentation/git-cvsserver.txt

@@ -133,6 +133,9 @@ write access to the log file and to the database (see

133 <<dbbackend,Database Backend>>. If you want to offer write access over

134 SSH, the users of course also need write access to the git repository itself.

135

136 +You also need to ensure that each repository is "bare" (without a git index

137 +file) for `cvs commit` to work. See linkgit:gitcvs-migration[7].

138 +

139 [[configaccessmethod]]

140 All configuration variables can also be overridden for a specific method of

141 access. Valid method names are "ext" (for SSH access) and "pserver". The

Documentation/gitcvs-migration.txt

@@ -143,6 +143,11 @@ work, you must not modify the imported branches; instead, create new

143 branches for your own changes, and merge in the imported branches as

144 necessary.

145

146 +If you want a shared repository, you will need to make a bare clone

147 +of the imported directory, as described above. Then treat the imported

148 +directory as another development clone for purposes of merging

149 +incremental imports.

150 +

151 Advanced Shared Repository Management

152 -------------------------------------

153