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. 516171b39a123033dbcaad620327ab14137cb569 Date: Fri, 21 Jun 2024 08:37:40 +0000 (GMT) [thread overview] Message-ID: <20240621083740.5EDA73896C2F@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 516171b39a123033dbcaad620327ab14137cb569 (commit) from b3c91409928d5aa68bde6649eff499a344e0b318 (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 516171b39a123033dbcaad620327ab14137cb569 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Fri Jun 21 10:37:04 2024 +0200 Add a closing parenthesis. diff --git a/htdocs/branch-closing.html b/htdocs/branch-closing.html index c18ea46b..fd109c2f 100644 --- a/htdocs/branch-closing.html +++ b/htdocs/branch-closing.html @@ -54,7 +54,7 @@ is listed in "Known to work" or "Known to fail" as applicable.</li> <li>If the bug is a regression that is not fixed on all subsequent release branches and on trunk then it needs to remain open. Remove the version number of the branch being closed from the summary (for -example, change "[7/8 Regression]" to "[8 Regression]". If the +example, change "[7/8 Regression]" to "[8 Regression]"). If the milestone is not set, or is set to a version from the branch being closed, set it to the version number of the next release from the next oldest release branch. ----------------------------------------------------------------------- Summary of changes: htdocs/branch-closing.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-06-21 8:37 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=20240621083740.5EDA73896C2F@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).