@matheusbsbs / matheus-bagliano / commits / 0f76a543e3
Fork 0

cvsserver: Reword documentation on necessity of write access

Reworded the section about git-cvsserver needing to update the database. Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de> Signed-off-by: Junio C Hamano <junkio@cox.net>

Frank Lichtenheld committed Apr 12, 2007 at 16:43 UTC 0f76a543e398b116882a49fc115273988cc9eb29
1 file changed +9 -3
Documentation/git-cvsserver.txt
+9 -3
@@ -114,8 +114,14 @@ git-cvsserver uses one database per git head (i.e. CVS module) to
114 store information about the repository for faster access. The
115 database doesn't contain any persitent data and can be completly
116 regenerated from the git repository at any time. The database
117 -needs to be updated (i.e. written to) after every commit. That
118 -means that even if you offer only read access (e.g. by using
117 +needs to be updated (i.e. written to) after every commit.
118 +
119 +If the commit is done directly by using git (as opposed to
120 +using git-cvsserver) the update will need to happen on the
121 +next repository access by git-cvsserver, independent of
122 +access method and requested operation.
123 +
124 +That means that even if you offer only read access (e.g. by using
125 the pserver method), git-cvsserver should have write access to
126 the database to work reliably (otherwise you need to make sure
127 that the database if up-to-date all the time git-cvsserver is run).
@@ -125,7 +131,7 @@ By default it uses SQLite databases in the git directory, named
131 temporary files in the same directory as the database file on
132 write so it might not be enough to grant the users using
133 git-cvsserver write access to the database file without granting
128 -them also write access to the directory.
134 +them write access to the directory, too.
135
136 You can configure the database backend with the following
137 configuration variables: