From: Junio C Hamano <junio@pobox.com>
To: Scott Collins <scc@ScottCollins.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clarify documentation of git-cvsserver, particularly in relation to git-shell
Date: Wed, 16 Apr 2008 13:03:40 -0700 [thread overview]
Message-ID: <7vhce1pnxf.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1208295883-19599-1-git-send-email-scc@ScottCollins.net
Scott Collins <scc@ScottCollins.net> 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.
next prev parent reply other threads:[~2008-04-16 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 15:30 [PATCH] Clarify documentation of git-cvsserver, particularly in relation to git-shell Scott Collins
2008-04-15 18:27 ` Junio C Hamano
2008-04-15 19:33 ` Scott Collins
2008-04-15 21:03 ` Scott Collins
2008-04-19 15:43 ` Johannes Schindelin
2008-04-15 21:44 ` Scott Collins
2008-04-16 20:03 ` Junio C Hamano [this message]
2008-04-19 15:45 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vhce1pnxf.fsf@gitster.siamese.dyndns.org \
--to=junio@pobox.com \
--cc=git@vger.kernel.org \
--cc=scc@ScottCollins.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).