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. 754efd283277cfd3a0a10a496729e6c96376c2f3
Date: Thu, 16 Jan 2020 21:43:00 -0000	[thread overview]
Message-ID: <20200116214307.7376.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  754efd283277cfd3a0a10a496729e6c96376c2f3 (commit)
      from  b45940f0b3841bc286fd18ffd312a9e297b2859c (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 754efd283277cfd3a0a10a496729e6c96376c2f3
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Jan 16 22:42:42 2020 +0100

    Promote Git on our home page.

diff --git a/htdocs/index.html b/htdocs/index.html
index 89bcfcca..41bcfe18 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -32,7 +32,7 @@ of native and cross targets (including GNU/Linux), and encourage everyone
 to <a href="contribute.html">contribute</a> changes or help
 <a href="testing/">testing</a> GCC.
 Our sources are readily and freely available via
-<a href="svn.html">SVN</a> and weekly
+<a href="git.html">Git</a> and weekly
 <a href="snapshots.html">snapshots</a>.</p>
 
 <p>Major decisions about GCC are made by the <a href="steering.html">

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

Summary of changes:
 htdocs/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-16 21:43 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=20200116214307.7376.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).