From: Richard Bunt <richard.bunt@linaro.org>
To: gdb-patches@sourceware.org
Cc: Richard Bunt <richard.bunt@linaro.org>
Subject: [PATCH] gdb: add Richard Bunt to gdb/MAINTAINERS
Date: Fri, 19 May 2023 12:59:40 +0100 [thread overview]
Message-ID: <20230519115940.3392691-1-richard.bunt@linaro.org> (raw)
---
gdb/MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index 175595d5f17..184e57b9651 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -479,6 +479,7 @@ Paul Brook paul@codesourcery.com
Julian Brown julian@codesourcery.com
Iain Buclaw ibuclaw@gdcproject.org
Kevin Buettner kevinb@redhat.com
+Richard Bunt richard.bunt@linaro.org
Andrew Burgess aburgess@redhat.com
David Carlton carlton@bactrian.org
Stephane Carrez Stephane.Carrez@gmail.com
--
2.32.0
next reply other threads:[~2023-05-19 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 11:59 Richard Bunt [this message]
2023-05-19 22:40 ` Maciej W. Rozycki
2023-05-22 10:51 ` Richard Bunt
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=20230519115940.3392691-1-richard.bunt@linaro.org \
--to=richard.bunt@linaro.org \
--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).