From: Nick Clifton via Gdb-patches <gdb-patches@sourceware.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] MAINTAINERS: Update path to readline config.{sub,guess} files
Date: Mon, 24 May 2021 14:54:54 +0100 [thread overview]
Message-ID: <625ee02d-9eeb-12fc-e340-72800922461b@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2105232311000.31561@angie.orcam.me.uk>
Hi Maciej,
> There is a note at the top of MAINTAINERS asking that ChangeLog entries
> be not made for updates to this file, however I can see they have been.
Weird. I see that note too, but I have no idea why it is there.
> What shall I do then?
Go ahead and include a ChangeLog update. If it really matters it can be
removed in the future, but personally I can think of no good reason for
not documenting changes.
> I take it the change is otherwise obvious.
Agreed. Please apply.
Cheers
Nick
next prev parent reply other threads:[~2021-05-24 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 21:32 Maciej W. Rozycki
2021-05-24 13:54 ` Nick Clifton via Gdb-patches [this message]
2021-05-24 15:22 ` Tom Tromey
2021-05-24 16:15 ` Maciej W. Rozycki
2021-06-07 13:39 kerenyi&qwertynet hu
2021-06-09 15:36 kerenyi&qwertynet hu
2021-06-15 16:23 Nick Clifton via Gdb-patches
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=625ee02d-9eeb-12fc-e340-72800922461b@redhat.com \
--to=gdb-patches@sourceware.org \
--cc=binutils@sourceware.org \
--cc=macro@orcam.me.uk \
--cc=nickc@redhat.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