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. 335d0b9345d12398b14ad6f69c3572861ce49d5b
Date: Wed, 15 Jan 2020 21:35:00 -0000	[thread overview]
Message-ID: <20200115213548.4584.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  335d0b9345d12398b14ad6f69c3572861ce49d5b (commit)
      from  75712dd8e232984cc6eb7dc9aee1aeddfb54bbe7 (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 335d0b9345d12398b14ad6f69c3572861ce49d5b
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Wed Jan 15 22:34:53 2020 +0100

    Swap links to our previous SVN documentation with those for Git.

diff --git a/htdocs/style.mhtml b/htdocs/style.mhtml
index 0026d6c4..677fd05a 100644
--- a/htdocs/style.mhtml
+++ b/htdocs/style.mhtml
@@ -109,8 +109,8 @@
   <tr><td><table class="navitem">
   <tr><td>Sources</td></tr>
   <tr><td>
-  <a href="<get-var BACKPATH>svn.html">SVN read access</a><br />
-  <a href="<get-var BACKPATH>svnwrite.html">SVN write access</a><br />
+  <a href="<get-var BACKPATH>git.html">Git</a><br />
+  <a href="<get-var BACKPATH>gitwrite.html">...write access</a><br />
   <a href="<get-var BACKPATH>rsync.html">Rsync</a><br />
   </td></tr>
   </table></td></tr>

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

Summary of changes:
 htdocs/style.mhtml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-15 21:35 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=20200115213548.4584.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).