From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org, Simon Marchi <simark@simark.ca>
Subject: Re: [RFA] Rename gdb/ChangeLog to gdb/ChangeLog-2021
Date: Tue, 6 Jul 2021 09:16:58 -0700 [thread overview]
Message-ID: <20210706161658.GA12614@adacore.com> (raw)
In-Reply-To: <f6daccd1-17f7-d11a-4424-a554d9841620@polymtl.ca>
> > Now that ChangeLog entries are no longer used for GDB patches,
> > this commit renames the file gdb/ChangeLog to gdb/ChangeLog-2021,
> > similar to what we would do in the context of the "Start of New
> > Year" procedure.
> >
> > The purpose of this change is to avoid people merging ChangeLog
> > entries by mistake when applying existing commits that they are
> > currently working on.
> >
> > OK to apply to master? (maybe a bit on the obvious side, but
> > this also allows us to make sure I am not missing something
> > in the commit message)
>
> Thanks, that LGTM.
Thank you all. Now pushed!
--
Joel
next prev parent reply other threads:[~2021-07-06 16:17 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
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 [this message]
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=20210706161658.GA12614@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@polymtl.ca \
/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).