From: Gerald Pfeifer <gerald@pfeifer.com>
To: Kelley Cook <kelleycook@yahoo.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Zack Weinberg <zack@codesourcery.com>,
Chiaki <ishikawa@yk.rim.or.jp>
Subject: Re: Please mention the CVS parameter has changed in the web page
Date: Wed, 21 Jan 2004 15:29:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.58.0401211601110.45880@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <400E8A95.6030600@ford.com>
On Wed, 21 Jan 2004, Kelley Cook wrote:
> I believe that our instructions for accessing Savannah are missing a few
> steps which any GCC developers likely wouldn't have noticed, since they
> were already required for our cvs write access.
>
> a) You must have SSHv2 installed.
> b) You must set CVS_RSH="ssh".
This patch is mostly fine, thanks.
Some issues I noticed: Please do not link to any SSH implementation and
use the term "SSH2 protocol". (In fact, I'd simply omit that -- hardly
any client these days does not support SSH2, so this may confuse more
users than it helps.)
The update of the page you refer to happened in January this year.
Both items 3 and 4 are optional, in the sense that one doesn't need to
do 3 to do 4. I suggest to merge these two items and use the original
wording (or something like that).
Gerald
--
Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2004-01-21 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 6:10 Please mention the CVS parameter has changed in the web page explicitly. Also a GCC source mirror? Chiaki
2004-01-21 7:10 ` Zack Weinberg
2004-01-21 7:24 ` Chiaki
2004-01-21 14:27 ` Please mention the CVS parameter has changed in the web page Kelley Cook
2004-01-21 15:29 ` Gerald Pfeifer [this message]
2004-01-21 16:47 ` Kelley Cook
2004-01-21 18:16 ` Gerald Pfeifer
2004-01-21 16:54 ` Chiaki
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSF.4.58.0401211601110.45880@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=ishikawa@yk.rim.or.jp \
--cc=kelleycook@yahoo.com \
--cc=zack@codesourcery.com \
/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.
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).