From: Martin Galvan <martin.galvan@tallertechnologies.com>
To: overseers@sourceware.org,
Martin Galvan <martin.galvan@tallertechnologies.com>
Cc: Doug Evans <dje@google.com>
Subject: Re: Request from Martin Galvan
Date: Tue, 26 May 2015 14:37:00 -0000 [thread overview]
Message-ID: <CAOKbPbaGiWp75mcX-m2vkjOxzJr+oVOeQ6=OGd3DZ0e+Srck_A@mail.gmail.com> (raw)
In-Reply-To: <20150526142929.GA5707@ednor.casa.cgf.cx>
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?
--
Martin Galvan
Software Engineer
Taller Technologies Argentina
San Lorenzo 47, 3rd Floor, Office 5
Córdoba, Argentina
Phone: 54 351 4217888 / +54 351 4218211
next prev parent reply other threads:[~2015-05-26 14:37 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 [this message]
2015-05-26 17:15 ` Doug Evans
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='CAOKbPbaGiWp75mcX-m2vkjOxzJr+oVOeQ6=OGd3DZ0e+Srck_A@mail.gmail.com' \
--to=martin.galvan@tallertechnologies.com \
--cc=dje@google.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).