diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2009-11-23 11:09:27 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2009-11-23 11:09:27 +0000 |
| commit | 9df0c66308c7d858d04f0ac7916bc4efe87b4486 (patch) | |
| tree | 61d0593b43d0558a066f7e3e3d32e15b7c14fd03 /git-cvsserver.txt | |
| parent | bf984de67c8dac8e5143a680957a4c5f95d0078f (diff) | |
| download | git-htmldocs-9df0c66308c7d858d04f0ac7916bc4efe87b4486.tar.gz | |
Autogenerated HTML docs for v1.6.6-rc0-15-g4fa80
Diffstat (limited to 'git-cvsserver.txt')
| -rw-r--r-- | git-cvsserver.txt | 19 |
1 files changed, 15 insertions, 4 deletions
diff --git a/git-cvsserver.txt b/git-cvsserver.txt index 785779e22..99a7c1470 100644 --- a/git-cvsserver.txt +++ b/git-cvsserver.txt @@ -182,10 +182,9 @@ Database Backend ---------------- 'git-cvsserver' uses one database per git head (i.e. CVS module) to -store information about the repository for faster access. The -database doesn't contain any persistent data and can be completely -regenerated from the git repository at any time. The database -needs to be updated (i.e. written to) after every commit. +store information about the repository to maintain consistent +CVS revision numbers. The database needs to be +updated (i.e. written to) after every commit. If the commit is done directly by using `git` (as opposed to using 'git-cvsserver') the update will need to happen on the @@ -204,6 +203,18 @@ write so it might not be enough to grant the users using 'git-cvsserver' write access to the database file without granting them write access to the directory, too. +The database can not be reliably regenerated in a +consistent form after the branch it is tracking has changed. +Example: For merged branches, 'git-cvsserver' only tracks +one branch of development, and after a 'git-merge' an +incrementally updated database may track a different branch +than a database regenerated from scratch, causing inconsistent +CVS revision numbers. `git-cvsserver` has no way of knowing which +branch it would have picked if it had been run incrementally +pre-merge. So if you have to fully or partially (from old +backup) regenerate the database, you should be suspicious +of pre-existing CVS sandboxes. + You can configure the database backend with the following configuration variables: |