public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 8908be1f4f140ccee72ebaec9bfc66c4aa6b033e
Date: Wed,  1 Dec 2021 21:10:35 +0000 (GMT)	[thread overview]
Message-ID: <20211201211035.5B532385841D@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  8908be1f4f140ccee72ebaec9bfc66c4aa6b033e (commit)
      from  f4b4d0f783246dd6f58944cdb542446d5e7589d3 (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 8908be1f4f140ccee72ebaec9bfc66c4aa6b033e
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Wed Dec 1 23:09:38 2021 +0200

    gcc-12: Update link to our Bugzilla
    
    On the way tweak language a bit.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 45a8d99a..000501fb 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -399,7 +399,7 @@ a work-in-progress.</p>
     has been rewritten to be easier and less error-prone to maintain.  Every
     attempt has been made to ensure that the new behavior matches the old
     behavior, but inevitably some bugs can be expected.  Please report any
-    problems using <a href="https://gcc.gnu.org/bugzilla">GCC Bugzilla</a>.
+    problems via <a href="https://gcc.gnu.org/bugzilla/">GCC Bugzilla</a>.
   </li>
   <li>
     The built-in functions <code>__builtin_get_texasr</code>,

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2021-12-01 21:10 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=20211201211035.5B532385841D@sourceware.org \
    --to=gerald@sourceware.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).