From: Simon Marchi <simark@simark.ca>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [release/HEAD 2/2] Update NEWS post GDB 11 branch creation.
Date: Sat, 3 Jul 2021 18:09:56 -0400 [thread overview]
Message-ID: <78121a45-b38a-61b1-4371-e271bb67e03e@simark.ca> (raw)
In-Reply-To: <20210703175454.1426972-3-brobecker@adacore.com>
On 2021-07-03 1:54 p.m., Joel Brobecker wrote:
> gdb/ChangeLog:
>
> * NEWS: Create a new section for the next release branch.
> Rename the section of the current branch, now that it has
> been cut.
Hi Joel,
Since we are not going to use the ChangeLog file on the master branch
from now on, should we maybe rename it to ChangeLog-2021 right away?
That would avoid people merging ChangeLog entries by mistake (it would
be confusing to have some people merge ChangeLog entries for the patches
they have in progress and others not).
Simon
next prev parent reply other threads:[~2021-07-03 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 17:54 FYI/HEAD: Patches applied to branch master Joel Brobecker
2021-07-03 17:54 ` [release/HEAD 1/2] Bump version to 12.0.50.DATE-git Joel Brobecker
2021-07-03 17:54 ` [release/HEAD 2/2] Update NEWS post GDB 11 branch creation Joel Brobecker
2021-07-03 22:09 ` Simon Marchi [this message]
2021-07-03 23:27 ` Joel Brobecker
2021-07-03 23:32 ` [RFA] Rename gdb/ChangeLog to gdb/ChangeLog-2021 Joel Brobecker
2021-07-04 4:28 ` Eli Zaretskii
2021-07-04 22:47 ` Simon Marchi
2021-07-06 16:16 ` Joel Brobecker
2021-07-08 7:45 ` Tom de Vries
2021-07-08 12:56 ` Joel Brobecker
2021-08-18 0:29 ` Mike Frysinger
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=78121a45-b38a-61b1-4371-e271bb67e03e@simark.ca \
--to=simark@simark.ca \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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: 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).