From: Alan Hayward <Alan.Hayward@arm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH OBV] Add myself as a write-after-approval GDB maintainer.
Date: Fri, 26 Jan 2018 15:47:00 -0000 [thread overview]
Message-ID: <B40ACF6E-C157-421D-8F28-285DCA46B26C@arm.com> (raw)
In-Reply-To: <CAH=s-PNA-b7a_ZF1V_XH=EfwwXqcPAVoRH1tAtOPw2DqrmgCXA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1608 bytes --]
Sorry! Fixed now. I think I mistook the âa" in Harris as an âeâ.
gdb/
* MAINTAINERS (Write After Approval): Fix ordering.
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index 4202608..0aafe11 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -506,8 +506,8 @@ Matthew Green mrg@eterna.com.au
Matthew Gretton-Dann matthew.gretton-dann@arm.com
Maxim Grigoriev maxim2405@gmail.com
Jerome Guitton guitton@act-europe.fr
-Alan Hayward alan.hayward@arm.com
Ben Harris bjh21@netbsd.org
+Alan Hayward alan.hayward@arm.com
Bernhard Heckel heckel_bernhard@web.de
Richard Henderson rth@redhat.com
Aldy Hernandez aldyh@redhat.com
> On 26 Jan 2018, at 15:17, Yao Qi <qiyaoltc@gmail.com> wrote:
>
> On Fri, Jan 26, 2018 at 2:48 PM, Alan Hayward <Alan.Hayward@arm.com> wrote:
>> +Alan Hayward alan.hayward@arm.com
>> Ben Harris bjh21@netbsd.org
>> Bernhard Heckel heckel_bernhard@web.de
>> Richard Henderson rth@redhat.com
>
> This list is sorted by the order of last name, so your name should
> be put after "Ben Harris".
>
> --
> Yao (é½å°§)
\x16º&Öéj×!zÊÞ¶êç×t÷Ib²Ö«r\x18\x1dnr\x17¬
prev parent reply other threads:[~2018-01-26 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 14:48 Alan Hayward
2018-01-26 15:18 ` Yao Qi
2018-01-26 15:47 ` Alan Hayward [this message]
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=B40ACF6E-C157-421D-8F28-285DCA46B26C@arm.com \
--to=alan.hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=qiyaoltc@gmail.com \
/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