diff options
Diffstat (limited to 'man1/git-cvsserver.1')
| -rw-r--r-- | man1/git-cvsserver.1 | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/man1/git-cvsserver.1 b/man1/git-cvsserver.1 index c8ddcfea4..65d33842a 100644 --- a/man1/git-cvsserver.1 +++ b/man1/git-cvsserver.1 @@ -2,12 +2,12 @@ .\" Title: git-cvsserver .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author] .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/> -.\" Date: 2024-02-06 +.\" Date: 2024-02-08 .\" Manual: Git Manual -.\" Source: Git 2.43.0.561.g235986be82 +.\" Source: Git 2.43.0.581.g5216f8f5c4 .\" Language: English .\" -.TH "GIT\-CVSSERVER" "1" "2024\-02\-06" "Git 2\&.43\&.0\&.561\&.g235986" "Git Manual" +.TH "GIT\-CVSSERVER" "1" "2024\-02\-08" "Git 2\&.43\&.0\&.581\&.g5216f8" "Git Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -320,7 +320,7 @@ Clients should now be able to check out the project\&. Use the CVS name to indicate what Git \fIhead\fR you want to check out\&. This also sets the name of your newly checked\-out directory, unless you tell it otherwise with -\fB\-d <dir_name>\fR\&. For example, this checks out +\fB\-d <dir\-name>\fR\&. For example, this checks out \fImaster\fR branch to the \fBproject\-master\fR @@ -345,7 +345,7 @@ If the commit is done directly by using \fBgit\fR (as opposed to using \fIgit\-c .sp That means that even if you offer only read access (e\&.g\&. by using the pserver method), \fIgit\-cvsserver\fR should have write access to the database to work reliably (otherwise you need to make sure that the database is up to date any time \fIgit\-cvsserver\fR is executed)\&. .sp -By default it uses SQLite databases in the Git directory, named \fBgitcvs\&.<module_name>\&.sqlite\fR\&. Note that the SQLite backend creates temporary files in the same directory as the database file on write so it might not be enough to grant the users using \fIgit\-cvsserver\fR write access to the database file without granting them write access to the directory, too\&. +By default it uses SQLite databases in the Git directory, named \fBgitcvs\&.<module\-name>\&.sqlite\fR\&. Note that the SQLite backend creates temporary files in the same directory as the database file on write so it might not be enough to grant the users using \fIgit\-cvsserver\fR write access to the database file without granting them write access to the directory, too\&. .sp The database cannot be reliably regenerated in a consistent form after the branch it is tracking has changed\&. Example: For merged branches, \fIgit\-cvsserver\fR only tracks one branch of development, and after a \fIgit merge\fR an incrementally updated database may track a different branch than a database regenerated from scratch, causing inconsistent CVS revision numbers\&. \fBgit\-cvsserver\fR 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\&. .sp |