From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Sergei Trofimovich <slyfox@gentoo.org>,
Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: unconditionally define _initialize_string_view_selftests
Date: Mon, 18 Mar 2019 16:00:00 -0000 [thread overview]
Message-ID: <87o96841h6.fsf@tromey.com> (raw)
In-Reply-To: <87va0gq1jo.fsf@redhat.com> (Sergio Durigan Junior's message of "Sun, 17 Mar 2019 23:55:23 -0400")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
Sergio> I'm not a global maintainer, but I believe Tom wouldn't mind if you put
Sergio> him as the person who approved the request.
Indeed. The rule is you need one accepted patch to get
write-after-review access. If you go this route then you should send
and commit a patch to update the MAINTAINERS file to add your name.
thanks,
Tom
prev parent reply other threads:[~2019-03-18 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 22:28 Sergei Trofimovich
2019-03-15 14:24 ` Tom Tromey
2019-03-17 22:20 ` Sergei Trofimovich
2019-03-17 22:28 ` [PATCH v2] " Sergei Trofimovich
2019-03-18 4:02 ` Sergio Durigan Junior
2019-03-18 3:55 ` [PATCH] " Sergio Durigan Junior
2019-03-18 16:00 ` Tom Tromey [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=87o96841h6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=slyfox@gentoo.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