From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [committed][gdb] Make btrace maintainer entry more clear
Date: Mon, 9 May 2022 15:15:43 +0200 [thread overview]
Message-ID: <20220509131542.GA5405@delia> (raw)
Hi,
Do:
...
-record btrace <name> <email>
+record
+ btrace <name> <email>
...
to clarify that the listed maintainer is only maintainer of the btrace part of
record.
Committed to trunk.
Thanks,
- Tom
[gdb] Make btrace maintainer entry more clear
---
gdb/MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index 225c4b24722..700fd3cd8b4 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -389,7 +389,8 @@ SystemTap Sergio Durigan Junior sergiodj@sergiodj.net
Reverse debugging / Record and Replay / Tracing:
-record btrace Markus T. Metzger markus.t.metzger@intel.com
+record
+ btrace Markus T. Metzger markus.t.metzger@intel.com
reply other threads:[~2022-05-09 13:16 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=20220509131542.GA5405@delia \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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