public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. dff8f587116f9a81b545dad0557d3ae90e58a6d6 Date: Fri, 9 Apr 2021 10:03:46 +0000 (GMT) [thread overview] Message-ID: <20210409100346.C95FD385702E@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 dff8f587116f9a81b545dad0557d3ae90e58a6d6 (commit) from cf2c734b45f269743a849c3ff6401ceb8ad17901 (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 dff8f587116f9a81b545dad0557d3ae90e58a6d6 Author: Martin Liska <mliska@suse.cz> Date: Fri Apr 9 12:03:20 2021 +0200 Fix known-to-fail/works version. diff --git a/htdocs/branch-closing.html b/htdocs/branch-closing.html index 9e35acc1..2a4f9d21 100644 --- a/htdocs/branch-closing.html +++ b/htdocs/branch-closing.html @@ -43,7 +43,7 @@ and version-specific bugs for the branch being closed:</p> <ol> <li>Ensure that the version number of the branch at the time it is -closed (for example, "7.5" if the branch is being closed when that +closed (for example, "7.5.0" if the branch is being closed when that is the version number a compiler built from the branch would report) is listed in "Known to work" or "Known to fail" as applicable.</li> ----------------------------------------------------------------------- Summary of changes: htdocs/branch-closing.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-04-09 10:03 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=20210409100346.C95FD385702E@sourceware.org \ --to=marxin@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).