From: Junio C Hamano Date: Wed, 16 Apr 2008 20:03:40 GMT Subject: Re: [PATCH] Clarify documentation of git-cvsserver, particularly in relation to git-shell Message-ID: <7vhce1pnxf.fsf@gitster.siamese.dyndns.org> In-Reply-To: <1208295883-19599-1-git-send-email-scc@ScottCollins.net> Scott Collins writes: > For SSH clients restricted to git-shell, CVS_SERVER does not have to be > specified, because git-shell understands the default value of 'cvs' to > mean git-cvsserver'. This makes it totally transparent to CVS users, but > the instruction to set up CVS access for people with real shell access > does not apply. Thanks. I was only _guessing_ that the reasoning behind the "cvs" hack in git-shell was to allow a vanilla "cvs over ssh" to work transparently without trying, but it appears to work exactly that way. > > Note that the .ssh/environment file is a good place to set these, and that > the .bashrc is shell-specific. Add a bit of text to differentiate cvs -d > (setting CVSROOT) from cvs co -d (setting the name of the newly checked > out directory). Removed an extra 'Example:' string. Suggesting .ssh/environment as an alternative is a good idea, but not everybody's sshd pays attention to it, so the user still needs to learn how to drive his or her ssh environment. But this document is not a troubleshooting guide for ssh, so let's not go there too much. I think your description is fine.