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. 3e8c4b788a310070dab416f593458e9c46948cbd Date: Tue, 19 Apr 2022 08:57:43 +0000 (GMT) [thread overview] Message-ID: <20220419085743.9525E3857809@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 3e8c4b788a310070dab416f593458e9c46948cbd (commit) from 0f3295084b682c059ddc89449d933d1a5bfef5db (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 3e8c4b788a310070dab416f593458e9c46948cbd Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Apr 19 09:57:14 2022 +0100 Update branching.html with reminder for libstdc++ docs diff --git a/htdocs/branching.html b/htdocs/branching.html index f30a47e1..40d65271 100644 --- a/htdocs/branching.html +++ b/htdocs/branching.html @@ -40,6 +40,9 @@ git push origin tag basepoints/gcc-11 for the next major release in the <code>wwwdocs</code> repository and populate it with initial copies of <code>changes.html</code> and <code>criteria.html</code>.</li> + +<li>Notify libstdc++ maintainers to update references to "mainline GCC" in +<code>libstdc++-v3/doc/xml/manual/status_cxx*.xml</code>.</li> </ol> <h2>Web Site Updates</h2> ----------------------------------------------------------------------- Summary of changes: htdocs/branching.html | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-04-19 8:57 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=20220419085743.9525E3857809@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).