public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. cdc7bf90357701877546f8bac160d0fb9e20b334 Date: Wed, 09 Oct 2019 00:20:00 -0000 [thread overview] Message-ID: <20191009002037.108803.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via cdc7bf90357701877546f8bac160d0fb9e20b334 (commit) from d4506304338216a4a5fd741ebc43bc90c2238641 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit cdc7bf90357701877546f8bac160d0fb9e20b334 Author: Joseph Myers <joseph@codesourcery.com> Date: Wed Oct 9 00:20:20 2019 +0000 Document web pages as managed via git. diff --git a/htdocs/about.html b/htdocs/about.html index 19dd080..30a5c94 100644 --- a/htdocs/about.html +++ b/htdocs/about.html @@ -19,7 +19,7 @@ many <a href="https://gcc.gnu.org/onlinedocs/gcc/Contributors.html">contributors </a>.</p> -<p>The web pages are under <a href="#cvs">CVS control</a>. +<p>The web pages are under <a href="#git">git control</a>. The pages on gcc.gnu.org are updated directly after a change has been committed. www.gnu.org is updated once a day at 4:00 -0700 (PDT).</p> @@ -48,20 +48,16 @@ a higher chance of being implemented soon. ;-)</p> <hr /> -<h2 id="cvs">Using the CVS repository</h2> +<h2 id="git">Using the git repository</h2> -<p>Assuming you have both CVS +<p>Assuming you have both git and SSH installed, you can check out the web pages as follows:</p> <ol> - <li>Set CVS_RSH in your environment to <code>ssh</code>.</li> - <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> + <li><code>git clone git+ssh://<i>username</i>@gcc.gnu.org/sourceware/projects/gcc-home/wwwdocs.git</code> + where <i>username</i> is your user name at gcc.gnu.org</li> </ol> -<p>For anonymous access, use -<code>-d :pserver:cvs@gcc.gnu.org:/cvs/gcc</code> instead.</p> - <h3>Validating a change</h3> @@ -76,14 +72,14 @@ the <a href="https://validator.w3.org">W3 Validator</a>. Just use the and prefer that each checkin be of a complete, single logical change.</p> <ol> -<li>Sync your sources with the master repository via "<code>cvs -update</code>". +<li>Sync your sources with the master repository via "<code>git pull</code>". This will also identify any files in your local tree that you have modified.</li> -<li>We recommend reviewing the output of "<code>cvs diff</code>".</li> +<li>We recommend reviewing the output of "<code>git diff</code>".</li> -<li>Use "<code>cvs commit</code>" to check in the patch.</li> +<li>Use "<code>git commit</code>" and "<code>git push origin +master</code>" to check in the patch.</li> <li>Upon checkin a message will be sent to the gcc-cvs-wwwdocs mailing list.</li> diff --git a/htdocs/contribute.html b/htdocs/contribute.html index 91fa65a..499dfe8 100644 --- a/htdocs/contribute.html +++ b/htdocs/contribute.html @@ -152,7 +152,7 @@ validator.</p> <p>Please mark patches with the tag [wwwdocs] in the subject line.</p> -<p>More <a href="about.html#cvs">about our web pages</a>.</p> +<p>More <a href="about.html#git">about our web pages</a>.</p> <h2 id="patches">Submitting Patches</h2> diff --git a/htdocs/svn.html b/htdocs/svn.html index 5e93115..2b90966 100644 --- a/htdocs/svn.html +++ b/htdocs/svn.html @@ -22,7 +22,7 @@ GCC that is in our repository.</p> <p>In addition you can <a href="https://gcc.gnu.org/viewcvs/gcc/">browse our SVN history online</a>.</p> -<p>(Our <a href="about.html#cvs">web pages are managed via CVS</a>.)</p> +<p>(Our <a href="about.html#git">web pages are managed via git</a>.)</p> <h2>Using the SVN repository</h2> diff --git a/htdocs/svnwrite.html b/htdocs/svnwrite.html index 057a66a..1a22133 100644 --- a/htdocs/svnwrite.html +++ b/htdocs/svnwrite.html @@ -12,7 +12,7 @@ <p>We have read/write access to the SVN repository available for maintainers and significant developers.</p> -<p>Our <a href="about.html#cvs">web pages are managed via CVS</a>.</p> +<p>Our <a href="about.html#git">web pages are managed via git</a>.</p> <hr /> <h2>Contents</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/about.html | 22 +++++++++------------- htdocs/contribute.html | 2 +- htdocs/svn.html | 2 +- htdocs/svnwrite.html | 2 +- 4 files changed, 12 insertions(+), 16 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2019-10-09 0:20 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191009002037.108803.qmail@sourceware.org \ --to=jsm28@gcc.gnu.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).