public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 44d97225cc39f2cfbc3109c6a6473bde3886357a Date: Tue, 17 Aug 2021 20:30:40 +0000 (GMT) [thread overview] Message-ID: <20210817203040.C99B83982423@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 44d97225cc39f2cfbc3109c6a6473bde3886357a (commit) from b16ae164c47aaf65d70480b90f55fd9acdba5418 (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 44d97225cc39f2cfbc3109c6a6473bde3886357a Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Aug 17 21:30:28 2021 +0100 Add missing punctuation to <li> elements diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index 0a1b582a..99a1ddb1 100644 --- a/htdocs/bugs/index.html +++ b/htdocs/bugs/index.html @@ -102,11 +102,11 @@ three of which can be obtained from the output of <code>gcc -v</code>:</p> <li>An error that occurs only some of the times a certain file is compiled, such that retrying a sufficient number of times results in a successful compilation; this is a symptom of a hardware problem, - not of a compiler bug (sorry)</li> + not of a compiler bug (sorry).</li> <li>Assembly files (<code>*.s</code>) produced by the compiler, or any binary files, such as object files, executables, core files, or - precompiled header files</li> + precompiled header files.</li> <li>Duplicate bug reports, or reports of bugs already fixed in the development tree, especially those that have already been reported @@ -114,14 +114,14 @@ three of which can be obtained from the output of <code>gcc -v</code>:</p> <li>Bugs in the assembler, the linker or the C library. These are separate projects, with separate mailing lists and different bug - reporting procedures</li> + 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> + Project. Report them to whoever provided you with the release.</li> <li>Questions about the correctness or the expected behavior of certain constructs that are not GCC extensions. Ask them in forums - dedicated to the discussion of the programming language</li> + dedicated to the discussion of the programming language.</li> </ul> <h3 id="where">Where to post it</h3> ----------------------------------------------------------------------- Summary of changes: htdocs/bugs/index.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-08-17 20:30 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=20210817203040.C99B83982423@sourceware.org \ --to=redi@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).