public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tankut Baris Aktemur <aktemur@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Add myself to the gdb/MAINTAINERS write-after-approval list
Date: Wed, 23 Oct 2019 18:49:00 -0000 [thread overview]
Message-ID: <20191023184912.94666.qmail@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=bd888c0fe2cebbcab96d787387e0b32d301e0a2c
commit bd888c0fe2cebbcab96d787387e0b32d301e0a2c
Author: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
Date: Wed Oct 23 20:40:01 2019 +0200
Add myself to the gdb/MAINTAINERS write-after-approval list
gdb/ChangeLog:
2019-10-23 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
* MAINTAINERS (Write After Approval): Add Tankut Baris Aktemur.
Diff:
---
gdb/ChangeLog | 4 ++++
gdb/MAINTAINERS | 1 +
2 files changed, 5 insertions(+)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index fd8c939..53f50e2 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2019-10-23 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
+
+ * MAINTAINERS (Write After Approval): Add Tankut Baris Aktemur.
+
2019-10-23 Tom Tromey <tom@tromey.com>
* configure: Rebuild.
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index a963518..8898bb4 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -438,6 +438,7 @@ Pascal support Pierre Muller muller@sourceware.org
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
Pedro Alves pedro_alves@portugalmail.pt
David Anderson davea@sgi.com
John David Anglin dave.anglin@nrc-cnrc.gc.ca
next reply other threads:[~2019-10-23 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 18:49 Tankut Baris Aktemur [this message]
2022-11-16 23:27 Kévin Le Gouguec
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=20191023184912.94666.qmail@sourceware.org \
--to=aktemur@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).