From: Devang S <devang221129@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs]
Date: Fri, 01 Apr 2011 07:28:00 -0000 [thread overview]
Message-ID: <AANLkTimATeViocZTDnWjLTExu4ZKAuD0iSK3Syjx_Sxu@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinThhGOYmY8jCwuDk=8Fdo02Bwau6JD8wFoiX7M@mail.gmail.com>
Background/Test:
The cvs command <cvs -qz -d :ext:username@gcc.gnu.org:/cvs/gcc
checkout -P wwwdocs> needs to know the compression level while using
the -z option. Hence we need to provide compression level for network
traffic ranging from 0 to 9. 0 for default. This value for -z command
is not mentioned in the 2nd step. Hence it gives error.
On Fri, Apr 1, 2011 at 12:47 PM, Devang S <devang221129@gmail.com> 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.
>
>
> Changelog:
>
> Index: wwwdocs/htdocs/cvs.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/cvs.html,v
> retrieving revision 1.219
> diff -u -3 -r1.219 cvs.html
> --- wwwdocs/htdocs/cvs.html 8 Jan 2011 16:50:20 -0000 1.219
> +++ wwwdocs/htdocs/cvs.html 1 Apr 2011 07:01:58 -0000
> @@ -1,5 +1,6 @@
> <html>
>
> +
> <head>
> <meta name="description" content="Access to the GCC web pages via CVS" />
> <meta name="keywords" content="CVS, version control, GCC, source,
> public, repository" />
> @@ -21,7 +22,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 -qz 0 -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>
>
> ===================================================================
>
>
>
> --
> Cheers,
> Devang S
> http://celeritas9.wordpress.com
--
Thanks,
Devang S
http://celeritas9.wordpress.com
next prev parent reply other threads:[~2011-04-01 7:28 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 ` Devang S [this message]
2011-04-03 13:00 ` [wwwdocs] Gerald Pfeifer
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=AANLkTimATeViocZTDnWjLTExu4ZKAuD0iSK3Syjx_Sxu@mail.gmail.com \
--to=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).