public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb: move a write after approval entry into the correct place
Date: Tue, 6 Sep 2022 08:50:09 +0000 (GMT) [thread overview]
Message-ID: <20220906085009.DF81A3853553@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0908f111fc3a4ae1469a2f52aaa5834cada7e106
commit 0908f111fc3a4ae1469a2f52aaa5834cada7e106
Author: Andrew Burgess <aburgess@redhat.com>
Date: Tue Sep 6 09:47:04 2022 +0100
gdb: move a write after approval entry into the correct place
Noticed in passing that an entry in the MAINTAINERS write after
approval list was in the wrong place.
Diff:
---
gdb/MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index 00b9a5ce5e8..e4d28711f10 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -451,7 +451,6 @@ To get recommended for the Write After Approval list you need a valid
FSF assignment and have submitted one good patch.
Tankut Baris Aktemur tankut.baris.aktemur@intel.com
-Mihails Strasuns mihails.strasuns@intel.com
David Anderson davea@sgi.com
John David Anglin dave.anglin@nrc-cnrc.gc.ca
Andreas Arnez arnez@linux.ibm.com
@@ -667,6 +666,7 @@ David Smith dsmith@redhat.com
Stephen P. Smith ischis2@cox.net
Jackie Smith Cashion jsmith@redhat.com
Petr Sorfa petrs@caldera.com
+Mihails Strasuns mihails.strasuns@intel.com
Andrew Stubbs ams@codesourcery.com
Emi Suzuki emi-suzuki@tjsys.co.jp
Alfred M. Szmidt ams@gnu.org
reply other threads:[~2022-09-06 8:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220906085009.DF81A3853553@sourceware.org \
--to=aburgess@sourceware.org \
--cc=gdb-cvs@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).