summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 0f047f3)
raw | patch | inline | side by side (parent: 0f047f3)
author | Jean-Luc Herren <jlh@gmx.ch> | |
Thu, 31 Jan 2008 02:06:04 +0000 (03:06 +0100) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Thu, 31 Jan 2008 02:50:41 +0000 (18:50 -0800) |
Signed-off-by: Jean-Luc Herren <jlh@gmx.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-cvsserver.txt | patch | blob | history |
index c831548d4abfe8c2da7c8fc9b033d56b94f7a6cd..d3e99931d7d344cdfb04b90133dd926a2aac1c9b 100644 (file)
That means that even if you offer only read access (e.g. by using
the pserver method), git-cvsserver should have write access to
the database to work reliably (otherwise you need to make sure
-that the database if up-to-date all the time git-cvsserver is run).
+that the database is up-to-date any time git-cvsserver is executed).
By default it uses SQLite databases in the git directory, named
`gitcvs.<module_name>.sqlite`. Note that the SQLite backend creates