From: Frank Lichtenheld Date: Sun, 27 May 2007 12:33:07 +0000 (+0200) Subject: cvsserver: Note that CVS_SERVER can also be specified as method variable X-Git-Tag: v1.5.2.1~6 X-Git-Url: https://git.tokkee.org/?a=commitdiff_plain;h=548428954aa088aecd88805aa5a8e64aee0d3e8b;p=git.git cvsserver: Note that CVS_SERVER can also be specified as method variable Reasonably new versions of the cvs CLI client allow one to specifiy CVS_SERVER as a method variable directly in CVSROOT. This is way more convinient than using an environment variable since it gets saved in CVS/Root. Since I only discovered this by accident I guess there might be others out there that learnt CVS on the 1.11 series (or even earlier) and profit from such a note about cvs improvements in the last couple years. Signed-off-by: Frank Lichtenheld Signed-off-by: Junio C Hamano --- diff --git a/Documentation/git-cvsserver.txt b/Documentation/git-cvsserver.txt index 9f0d99080..ca7579d9f 100644 --- a/Documentation/git-cvsserver.txt +++ b/Documentation/git-cvsserver.txt @@ -57,7 +57,17 @@ looks like ------ No special setup is needed for SSH access, other than having GIT tools in the PATH. If you have clients that do not accept the CVS_SERVER -env variable, you can rename git-cvsserver to cvs. +environment variable, you can rename git-cvsserver to cvs. + +Note: Newer cvs versions (>= 1.12.11) also support specifying +CVS_SERVER directly in CVSROOT like + +------ +cvs -d ":ext;CVS_SERVER=git-cvsserver:user@server/path/repo.git" co +------ +This has the advantage that it will be saved in your 'CVS/Root' files and +you don't need to worry about always setting the correct environment +variable. -- 2. For each repo that you want accessible from CVS you need to edit config in the repo and add the following section.