From: Stafford Horne <shorne@gmail.com>
To: GDB patches <gdb-patches@sourceware.org>
Cc: Stafford Horne <shorne@gmail.com>
Subject: Re: [PATCH 1/4] gdb: Add Stafford Horne as or1k maintainer.
Date: Tue, 26 Dec 2017 13:53:00 -0000 [thread overview]
Message-ID: <CAAfxs74Lp1UxpKmU0uSLvnLaKBG_sUdGPYRMWDLSnpQ8hVVCVA@mail.gmail.com> (raw)
In-Reply-To: <20171214061341.7797-2-shorne@gmail.com>
Hello,
Is this ok to commit?
On Thu, Dec 14, 2017 at 3:13 PM, Stafford Horne <shorne@gmail.com> wrote:
> Since I helped upstream openrisc I would like to claim responsibility to
> maintain it.
>
> gdb/ChangeLog:
>
> yyyy-mm-dd Stafford Horne <shorne@gmail.com>
>
> * (Responsible Maintainers): Add myself as or1k maintainer.
> ---
> gdb/MAINTAINERS | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
> index 4597972464..9f61d8dcfa 100644
> --- a/gdb/MAINTAINERS
> +++ b/gdb/MAINTAINERS
> @@ -290,6 +290,9 @@ the native maintainer when resolving ABI issues.
>
> ns32k Deleted
>
> + or1k --target=or1k-elf ,-Werror
> + Stafford Horne shorne@gmail.com
> +
> pa --target=hppa-elf ,-Werror
>
> powerpc --target=powerpc-eabi ,-Werror
> --
> 2.13.6
>
next prev parent reply other threads:[~2017-12-26 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 6:14 [PATCH 0/4] OpenRISC misc updates Stafford Horne
2017-12-14 6:14 ` [PATCH 1/4] gdb: Add Stafford Horne as or1k maintainer Stafford Horne
2017-12-26 13:53 ` Stafford Horne [this message]
2018-06-01 17:24 ` Simon Marchi
2018-06-03 3:26 ` Stafford Horne
2017-12-14 6:14 ` [PATCH 3/4] gdb: Add news entries for new or1k target Stafford Horne
2017-12-14 17:01 ` Eli Zaretskii
2017-12-14 6:14 ` [PATCH 2/4] sim: Add Stafford Horne as or1k maintainer Stafford Horne
2017-12-26 13:53 ` Stafford Horne
2018-06-01 17:25 ` Simon Marchi
2018-06-03 3:29 ` Stafford Horne
2017-12-14 6:14 ` [PATCH 4/4] gdb: Fix function parameter alignments in or1k-tdep.c Stafford Horne
2017-12-15 10:48 ` Yao Qi
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=CAAfxs74Lp1UxpKmU0uSLvnLaKBG_sUdGPYRMWDLSnpQ8hVVCVA@mail.gmail.com \
--to=shorne@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).