public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Add myself to gdb/MAINTAINERS
Date: Sun, 03 May 2020 14:02:34 -0400 [thread overview]
Message-ID: <ad23bda0db2b2bee506147701424b2ebfef8f55a@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT ad23bda0db2b2bee506147701424b2ebfef8f55a ***
commit ad23bda0db2b2bee506147701424b2ebfef8f55a
Author: Mihails Strasuns <mihails.strasuns@intel.com>
AuthorDate: Mon Apr 20 16:44:44 2020 +0200
Commit: Mihails Strasuns <mihails.strasuns@intel.com>
CommitDate: Mon Apr 20 16:44:44 2020 +0200
Add myself to gdb/MAINTAINERS
2020-04-20 Mihails Strasuns <mihails.strasuns@intel.com>
* MAINTAINERS (Write After Approval): Add myself.
Change-Id: I3f412e328b42dea875a6d7cb74fc55415865f134
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 53cb98d4e3..b023bfe4b2 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2020-04-20 Mihails Strasuns <mihails.strasuns@intel.com>
+
+ * MAINTAINERS (Write After Approval): Add myself.
+
2020-04-18 Tom Tromey <tom@tromey.com>
* windows-tdep.c (init_w32_command_list)
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index 629e9cd85f..b6c31f6a60 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -440,6 +440,7 @@ 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
Pedro Alves pedro_alves@portugalmail.pt
David Anderson davea@sgi.com
John David Anglin dave.anglin@nrc-cnrc.gc.ca
next reply other threads:[~2020-05-03 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 18:02 gdb-buildbot [this message]
2020-05-03 18:02 ` Failures on Fedora-i686, branch master gdb-buildbot
2020-05-03 18:22 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2020-05-03 18:36 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-05-03 18:55 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-05-03 19:19 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-05-03 19:41 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-05-04 14:26 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-05-09 9:26 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2020-05-09 11:15 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
-- strict thread matches above, loose matches on Subject: below --
2020-01-03 8:37 [binutils-gdb] Add myself to gdb/MAINTAINERS gdb-buildbot
2020-01-01 21:02 gdb-buildbot
2019-05-17 10:06 sergiodj+buildbot
2019-04-01 8:41 sergiodj+buildbot
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=ad23bda0db2b2bee506147701424b2ebfef8f55a@gdb-build \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-testers@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).