Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Anton Kolesov <Anton.Kolesov@synopsys.com>
To: gdb-patches@sourceware.org
Cc: Francois.Bedard@synopsys.com,	Anton Kolesov <Anton.Kolesov@synopsys.com>
Subject: [PATCH 2/2] Add myself as a write-after-approval GDB maintainer
Date: Wed, 31 Aug 2016 08:50:00 -0000	[thread overview]
Message-ID: <1472633399-32477-2-git-send-email-Anton.Kolesov@synopsys.com> (raw)
In-Reply-To: <1472633399-32477-1-git-send-email-Anton.Kolesov@synopsys.com>

gdb/ChangeLog:

	* MAINTAINERS (Write After Approval): Add Anton Kolesov.
---
 gdb/MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index 67e00f6..67d1168 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -572,6 +572,7 @@ Mark Kettenis					kettenis@gnu.org
 Marc Khouzam					marc.khouzam@ericsson.com
 Toshihito Kikuchi					k.toshihito@yahoo.de
 Jim Kingdon					kingdon@panix.com
+Anton Kolesov					anton.kolesov@synopsys.com
 Paul Koning					paul_koning@dell.com
 Marcin Kościelnicki				koriakin@0x04.net
 Jan Kratochvil					jan.kratochvil@redhat.com
-- 
2.8.1


  reply	other threads:[~2016-08-31  8:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31  8:50 [PATCH 1/2] arc: New Synopsys ARC port Anton Kolesov
2016-08-31  8:50 ` Anton Kolesov [this message]
2016-08-31 13:59 ` Pedro Alves
2016-09-01 19:54   ` Anton Kolesov
2016-09-05 18:56     ` Pedro Alves
2016-09-15 11:39     ` Pedro Alves
2016-09-16 17:12       ` [PATCH v2] " Anton Kolesov
2016-09-16 17:54         ` Pedro Alves
2016-09-16 18:32         ` Eli Zaretskii
2016-09-16 18:33           ` Pedro Alves
2016-09-19 12:37             ` [PATCH v3] " Anton Kolesov
2016-09-19 17:02               ` Eli Zaretskii
2016-09-21 15:40                 ` [PATCH v4] " Anton Kolesov
2016-09-21 16:17                   ` Pedro Alves
2016-09-21 17:29                     ` Anton Kolesov
2016-09-21 17:30                       ` Pedro Alves

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=1472633399-32477-2-git-send-email-Anton.Kolesov@synopsys.com \
    --to=anton.kolesov@synopsys.com \
    --cc=Francois.Bedard@synopsys.com \
    --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