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. 303c5592f31a73cc90e2a799fe0455873db512b2 Date: Sun, 12 Mar 2023 09:38:50 +0000 (GMT) [thread overview] Message-ID: <20230312093850.776423858D1E@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 303c5592f31a73cc90e2a799fe0455873db512b2 (commit) from 8a551dfcd1b64e7970b43c0a034972167564e062 (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 303c5592f31a73cc90e2a799fe0455873db512b2 Author: Jonathan Wakely <jwakely@redhat.com> Date: Sun Mar 12 10:34:21 2023 +0100 bugs: Clarify meaning of "not issued by" diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index 765d8c67..3744a28f 100644 --- a/htdocs/bugs/index.html +++ b/htdocs/bugs/index.html @@ -116,8 +116,9 @@ three of which can be obtained from the output of <code>gcc -v</code>:</p> separate projects, with separate mailing lists and different bug reporting procedures.</li> - <li>Bugs in releases or snapshots of GCC not issued by the GNU - Project. Report them to whoever provided you with the release.</li> + <li>Bugs in unofficial releases or snapshots of GCC not issued by + the GCC project. Report them to whoever provided you with that + version.</li> <li>Questions about the correctness or the expected behavior of certain constructs that are not GCC extensions. Ask them in forums ----------------------------------------------------------------------- Summary of changes: htdocs/bugs/index.html | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-03-12 9:38 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=20230312093850.776423858D1E@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: linkBe 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).