public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: jb@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. f5b29a8fdedd895613f7304227d877d5add1535d
Date: Wed, 13 Nov 2019 20:54:00 -0000	[thread overview]
Message-ID: <20191113205456.51316.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  f5b29a8fdedd895613f7304227d877d5add1535d (commit)
      from  177b6b2a5475bb148e61dd87af3680092fd1c1e2 (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 f5b29a8fdedd895613f7304227d877d5add1535d
Author: Janne Blomqvist <blomqvist.janne@gmail.com>
Date:   Wed Nov 13 22:53:08 2019 +0200

    Update info about getting config.guess and config.sub
    
    The URL nowadays contains a README instructing the user to fetch the
    files from a git repository (git.savannah.gnu.org). Reword to reflect
    that. Also change the URL from FTP to HTTPS.

diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index f9dbc18..d43f28f 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -591,14 +591,15 @@ below:</p>
 
 <ul>
 
-<li>config.guess, config.sub: The master copy of these files is at <a
-href="ftp://ftp.gnu.org/pub/gnu/config/">ftp://ftp.gnu.org/pub/gnu/config</a>.
-Proposed changes should be e-mailed to <a
-href="mailto:config-patches@gnu.org">config-patches@gnu.org</a>.  Only
-after the change makes it to the FTP site should the new files be
-installed in the GCC source tree, so that their version numbers remain
-meaningful and unique.  Don't install the patch, install the whole
-file.</li>
+<li>config.guess, config.sub: Instructions for getting the master copy
+of these files is
+at <a href="https://ftp.gnu.org/pub/gnu/config/">https://ftp.gnu.org/pub/gnu/config</a>.
+Proposed changes should be e-mailed
+to <a href="mailto:config-patches@gnu.org">config-patches@gnu.org</a>.
+Only after the change makes it to the HTTP site should the new files
+be installed in the GCC source tree, so that their version numbers
+remain meaningful and unique.  Don't install the patch, install the
+whole file.</li>
 
 <li>ltmain.sh, libtool.m4, ltoptions.m4, ltsugar.m4, ltversion.m4,
 lt~obsolete.m4, and formerly also ltconfig, ltcf-c.sh, ltcf-cxx.sh,

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

Summary of changes:
 htdocs/codingconventions.html |   17 +++++++++--------
 1 files changed, 9 insertions(+), 8 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2019-11-13 20:54 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=20191113205456.51316.qmail@sourceware.org \
    --to=jb@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).