From: Doug Evans <dje@google.com>
To: Martin Galvan <martin.galvan@tallertechnologies.com>
Cc: overseers@sourceware.org
Subject: Re: Request from Martin Galvan
Date: Tue, 26 May 2015 17:15:00 -0000 [thread overview]
Message-ID: <CADPb22QnGBv9tNLtY1mKNjCBLAWaB30Nk=d8P6hhj87H1ndkAg@mail.gmail.com> (raw)
In-Reply-To: <CAOKbPbaGiWp75mcX-m2vkjOxzJr+oVOeQ6=OGd3DZ0e+Srck_A@mail.gmail.com>
[sorry for the repeat, wasn't sure if overseers rejected text/html,
and I was sending from my phone]
On Tue, May 26, 2015 at 7:36 AM, Martin Galvan
<martin.galvan@tallertechnologies.com> wrote:
> On Tue, May 26, 2015 at 11:29 AM, Christopher Faylor
> <cgf-use-the-mailinglist-please@sourceware.org> wrote:
>> On Tue, May 26, 2015 at 01:02:08PM -0000, martin.galvan@tallertechnologies.com wrote:
>>>Martin Galvan would like to be added to sourceware.org.
>>>
>>>For more information, check out:
>>>http://sourceware.org/cgi-bin/pdw/queue.cgi
>>>
>>>Or, check the specific request here:
>>>http://sourceware.org/cgi-bin/pdw/details.cgi?file=5743400.52264
>>
>> Sorry but AFAICT Yao Qi is only a write-after-approval maintainer in
>> gcc and does not have the authority to sponsor you for that project.
>
> Ok. What about Doug Evans (dje@google.com) ? He also suggested I
> should get commit access for gdb. Should I fill out a new form with
> his e-mail instead of Yao's?
I can't offer anything for GCC (I'm assuming).
next prev parent reply other threads:[~2015-05-26 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 13:02 martin.galvan
2015-05-26 14:29 ` Christopher Faylor
2015-05-26 14:37 ` Martin Galvan
2015-05-26 17:15 ` Doug Evans [this message]
2015-05-26 16:34 ` Pedro Alves
2015-05-26 18:57 ` Christopher Faylor
2015-05-26 14:10 martin.galvan
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='CADPb22QnGBv9tNLtY1mKNjCBLAWaB30Nk=d8P6hhj87H1ndkAg@mail.gmail.com' \
--to=dje@google.com \
--cc=martin.galvan@tallertechnologies.com \
--cc=overseers@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).