From: "Jose E. Marchesi" <jemarch@gnu.org>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: cgen@sourceware.org
Subject: Re: updating ChangeLog policy to match binutils/gdb?
Date: Tue, 14 Sep 2021 23:10:35 +0200 [thread overview]
Message-ID: <87o88uvp6c.fsf@gnu.org> (raw)
In-Reply-To: <YUD502UbhsGOnGDu@vapier> (Mike Frysinger via Cgen's message of "Tue, 14 Sep 2021 15:36:51 -0400")
> On 29 Jun 2021 18:17, Jose E. Marchesi via Cgen wrote:
>> > the binutils & gdb projects are changing their ChangeLog policy: they won't
>> > be required anywhere, but people need to write detailed commit messages.
>> > can we update cgen to follow suit ?
>> >
>> > gdb: https://sourceware.org/pipermail/gdb-patches/2021-June/179872.html
>> > binutils: https://sourceware.org/pipermail/binutils/2021-June/117016.html
>>
>> I wouldn't object to such a change.
>>
>> (I will continue including ChangeLog entries in commit messages
>> anyway... after so many years I would feel "naked" without them ;))
>
> just want to double check before i start doing this ... it's OK if i omit
> ChangeLog entries now ?
If Frank doesn't object, I think it makes sense to follow what binutils
and GDB do, i.e. no ChangeLog entries required.
prev parent reply other threads:[~2021-09-14 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 1:39 Mike Frysinger
2021-06-29 16:17 ` Jose E. Marchesi
2021-09-14 19:36 ` Mike Frysinger
2021-09-14 21:10 ` Jose E. Marchesi [this message]
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=87o88uvp6c.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=cgen@sourceware.org \
--cc=jose.marchesi@oracle.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).