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. e8120aa3ecc3dec9c6ddcd3add2326e94fe5fb1e Date: Wed, 19 Aug 2020 14:41:50 +0000 (GMT) [thread overview] Message-ID: <20200819144150.E7C313857C4D@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 e8120aa3ecc3dec9c6ddcd3add2326e94fe5fb1e (commit) from b468e3fdfd164c473ae1cd3facfc9ec9af9d25a9 (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 e8120aa3ecc3dec9c6ddcd3add2326e94fe5fb1e Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Aug 19 15:41:44 2020 +0100 Remove stray '>' character diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index 66d9138f..a6631d8a 100644 --- a/htdocs/bugs/index.html +++ b/htdocs/bugs/index.html @@ -222,7 +222,7 @@ submit it according to our <a href="#where">generic instructions</a>. "<code>[Ada]</code>" tag in the subject.)</p> <h2 id="pch">Detailed bug reporting instructions when using a precompiled -header></h2> +header</h2> <p>If you're encountering a bug when using a precompiled header, the first thing to do is to delete the precompiled header, and try running ----------------------------------------------------------------------- Summary of changes: htdocs/bugs/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-08-19 14:41 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=20200819144150.E7C313857C4D@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).