From: Gerald Pfeifer <gerald@pfeifer.com>
To: Devang S <devang221129@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs]
Date: Sun, 03 Apr 2011 13:00:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1104031442390.6055@gerinyyl> (raw)
In-Reply-To: <AANLkTinThhGOYmY8jCwuDk=8Fdo02Bwau6JD8wFoiX7M@mail.gmail.com>
On Fri, 1 Apr 2011, Devang S wrote:
> Found a bug on the cvs.html web page. How to start the web page patching
> I followed the instruction on the http://gcc.gnu.org/cvs.html page,
> downloaded the wwwdocs via cvs, validated the web page to be updated.
> Now I want to commit the changes to the repo. But for that I need
> write access(obviously). Please let me know what I need to do to
> commit the changes. Or please can someone do that on my behalf? I can
> let you know the details to be made.
Thanks for the report and suggested patch, Devang.
Looking into this a bit more, I noticed that -z actually only is
used for the classic protocol, whereas when tunnelled through SSH
as is the case here, SSH already should take care of compression,
plus the amount of data here is small, so we can just simplify and
remove this option altogether. I went ahead and committed the patch
below
As for your other questions, just keep changes coming, and I, or
others depending on the area, will be happy to review and commit
them.
Gerald
Index: cvs.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
retrieving revision 1.219
diff -u -r1.219 cvs.html
--- cvs.html 8 Jan 2011 16:50:20 -0000 1.219
+++ cvs.html 3 Apr 2011 12:42:51 -0000
@@ -21,7 +21,7 @@
<ol>
<li>Set CVS_RSH in your environment to <code>ssh</code>.</li>
- <li><code>cvs -qz -d :ext:<i>username</i>@gcc.gnu.org:/cvs/gcc checkout
+ <li><code>cvs -q -d :ext:<i>username</i>@gcc.gnu.org:/cvs/gcc checkout
-P wwwdocs</code> where <i>username</i> is your user name at gcc.gnu.org</li>
</ol>
next prev parent reply other threads:[~2011-04-03 13:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinDZDXERp2sR8z_oOmhzyv=vxrGG9WgHg31ujgh@mail.gmail.com>
2011-04-01 7:17 ` [wwwdocs] Devang S
2011-04-01 7:28 ` [wwwdocs] Devang S
2011-04-03 13:00 ` Gerald Pfeifer [this message]
2009-03-23 13:11 [wwwdocs] Martin Jambor
2009-03-23 13:44 ` [wwwdocs] Richard Guenther
-- strict thread matches above, loose matches on Subject: below --
2005-05-21 23:00 [wwwdocs] Gerald Pfeifer
2005-05-24 0:33 ` [wwwdocs] Mark Mitchell
2005-05-28 3:44 ` [wwwdocs] Gabriel Dos Reis
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=alpine.LNX.2.00.1104031442390.6055@gerinyyl \
--to=gerald@pfeifer.com \
--cc=devang221129@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
/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).