From: Gerald Pfeifer <gerald@pfeifer.com>
To: Pokechu22 <pokechu022@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] [PATCH 1/4] branch-closing: Fix various typos
Date: Fri, 21 Jun 2024 10:38:04 +0200 (CEST) [thread overview]
Message-ID: <766c1962-1824-15da-5b13-187e114b40ea@pfeifer.com> (raw)
In-Reply-To: <CAEpCGDQK4nmnCN7iUs8DSHeqoNBRttEu4P+SUq=-rH=oQxf1tw@mail.gmail.com>
On Tue, 22 Mar 2022, Pokechu22 via Gcc-patches wrote:
> --- 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.
Thank you for pointing this out; I fixed this now.
Gerald
next prev parent reply other threads:[~2024-06-21 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 19:50 [wwwdocs] [PATCH 0/4] " Pokechu22
2022-03-22 19:52 ` [wwwdocs] [PATCH 1/4] branch-closing: " Pokechu22
2022-03-22 19:54 ` [wwwdocs] [PATCH 2/4] codingconventions: " Pokechu22
2022-03-22 19:54 ` [wwwdocs] [PATCH 3/4] codingrationale: " Pokechu22
2022-03-22 19:55 ` [wwwdocs] [PATCH 4/4] contribute: " Pokechu22
2024-06-21 21:27 ` Gerald Pfeifer
2024-06-19 6:20 ` [wwwdocs] [PATCH 3/4] codingrationale: " Gerald Pfeifer
2024-06-18 8:27 ` [wwwdocs] [PATCH 2/4] codingconventions: " Gerald Pfeifer
2024-06-21 8:38 ` Gerald Pfeifer [this message]
2022-03-29 22:48 ` [wwwdocs] [PATCH 0/4] " Pokechu22
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=766c1962-1824-15da-5b13-187e114b40ea@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pokechu022@gmail.com \
/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: link
Be 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).