public inbox for
help / color / mirror / Atom feed
From: Jonathan Wakely <>
Subject: gcc-wwwdocs branch master updated. 6404392bcf74d2af7d171cc1df9b5c001d2218f8
Date: Tue, 24 Aug 2021 17:06:36 +0000 (GMT)	[thread overview]
Message-ID: <> (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  6404392bcf74d2af7d171cc1df9b5c001d2218f8 (commit)
      from  44d97225cc39f2cfbc3109c6a6473bde3886357a (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 6404392bcf74d2af7d171cc1df9b5c001d2218f8
Author: Jonathan Wakely <>
Date:   Tue Aug 24 18:06:25 2021 +0100

    Fix grammar in gcc-11 release notes

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index b8bb2e69..6dec8856 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -148,8 +148,8 @@ You may also want to check out our
       This can produce up to 25% more compact debug information
       compared to earlier versions.
-      To take full advantage of DWARF version 5 GCC needs to be build
-      against binutils version 2.35.2 or higher.  When GCC is build
+      To take full advantage of DWARF version 5 GCC needs to be built
+      against binutils version 2.35.2 or higher.  When GCC is built
       against earlier versions of binutils GCC will still emit DWARF
       version 5 for most debuginfo data, but will generate version 4
       debug line tables (even when explicitly given <code>-gdwarf-5</code>).


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


                 reply	other threads:[~2021-08-24 17:06 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).