public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: gerald@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 200ec9893d313fc0377dfc1d3e149d7ed9621670
Date: Sat, 18 Jan 2020 11:31:00 -0000	[thread overview]
Message-ID: <20200118113137.26868.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  200ec9893d313fc0377dfc1d3e149d7ed9621670 (commit)
      from  375ae5823171ce5eb12af5e3e685d5b975cfdbcb (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 200ec9893d313fc0377dfc1d3e149d7ed9621670
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Sat Jan 18 12:30:42 2020 +0100

    Condense and trim three aspects of our snapshot instructions.
    
    This includes folding in a reference to our lists overview as a link
    into some other text, removing a long obsolete reference to age-old
    versions of the patch command, and skippking details that are covered
    by the gcc_update script.

diff --git a/htdocs/snapshots.html b/htdocs/snapshots.html
index 80d61e27..6567a857 100644
--- a/htdocs/snapshots.html
+++ b/htdocs/snapshots.html
@@ -21,20 +21,15 @@ progress.  Any given snapshot may generate incorrect code or even fail to
 build.</p>
 
 <p>If you plan on downloading and using snapshots, we highly recommend you
-subscribe to the GCC mailing lists.  See <a href="lists.html">
-mailing lists</a> on the main GCC page for instructions on how to subscribe.</p>
+subscribe to the GCC <a href="lists.html">mailing lists</a>.</p>
 
 <p>When using the diff files to update from older snapshots to newer snapshots,
 make sure to use "-E" and "-p" arguments to patch so that empty files are
-deleted and full pathnames are provided to patch.  If your version of
-patch does not support "-E", you'll need to get a newer version.  Also note
-that you may need autoconf, autoheader and various other programs if you use
-diff files to update from one snapshot to the next.</p>
+deleted and full pathnames are provided to patch.</p>
 
 <p><code>contrib/gcc_update</code> can be used to apply diffs between
 successive snapshot versions and preserve relations between generated
-files so that autoconf et al aren't needed. This is documented in
-comments in contrib/gcc_update.</p>
+files so that autoconf et al aren't needed.</p>
 
 <p>The program <code>sha512sum</code> &mdash; which is included with the 
 <a href="https://www.gnu.org/software/coreutils/">GNU Coreutils</a>

-----------------------------------------------------------------------

Summary of changes:
 htdocs/snapshots.html | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-18 11:31 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=20200118113137.26868.qmail@sourceware.org \
    --to=gerald@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: 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).