From: Quentin Neill <quentin.neill.gnu@gmail.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: Sebastian Pop <sebpop@gmail.com>,
overseers@gcc.gnu.org, qneill@sourceware.org
Subject: Re: Welcome to sourceware.org
Date: Thu, 18 Nov 2010 21:01:00 -0000 [thread overview]
Message-ID: <AANLkTinL5E4LRPQ39Fw28=AdnEHNkwc7K3OMxcrQ+S=L@mail.gmail.com> (raw)
In-Reply-To: <m3tyjffcsp.fsf@pepe.airs.com>
On Wed, Nov 17, 2010 at 8:58 PM, Ian Lance Taylor <ian@airs.com> wrote:
> Sebastian Pop <sebpop@gmail.com> writes:
>
>> Quentin has already sent such an email 7 days ago,
>> but I have not seen a response from overseers yet.
>>
>>>
>>> Sebastian, are you sponsoring Quentin for gcc write access?
>>
>> Yes, I am sponsoring Quentin for GCC write access.
>
> Sorry, I did not notice the earlier e-mail somehow.
>
> I have added Quentin to the gcc group. Quentin, you should now have
> access to the gcc repository.
Thanks Ian.
> Please add yourself to the MAINTAINERS file.
>
> Ian
Done.
--
Quentin
next prev parent reply other threads:[~2010-11-18 21:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100803203035.19633.qmail@sourceware.org>
2010-08-05 23:10 ` Quentin Neill
2010-08-06 8:30 ` Hans-Peter Nilsson
2010-08-06 13:28 ` Christopher Faylor
2010-08-06 16:46 ` Quentin Neill
2010-08-06 17:22 ` Christopher Faylor
2010-08-06 18:22 ` Quentin Neill
2010-11-09 21:59 ` Quentin Neill
2010-11-16 21:02 ` Quentin Neill
2010-11-17 6:54 ` Ian Lance Taylor
2010-11-17 15:05 ` Sebastian Pop
2010-11-18 4:58 ` Ian Lance Taylor
2010-11-18 21:01 ` Quentin Neill [this message]
2010-11-17 0:18 ` Quentin Neill
[not found] <20200402160227.0991B388A01F@sourceware.org>
2020-04-03 6:40 ` Cui, Lili
2020-04-03 11:16 ` Frank Ch. Eigler
[not found] <20110723180027.5293.qmail@sourceware.org>
2011-07-28 0:19 ` Philippe Waroquiers
2011-07-28 0:23 ` Frank Ch. Eigler
[not found] <20080322164357.32125.qmail@sourceware.org>
2008-03-22 19:17 ` Chris Demetriou
2008-03-22 20:05 ` Daniel Jacobowitz
2008-03-22 21:57 ` Christopher Faylor
2008-03-24 16:38 ` Chris Demetriou
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='AANLkTinL5E4LRPQ39Fw28=AdnEHNkwc7K3OMxcrQ+S=L@mail.gmail.com' \
--to=quentin.neill.gnu@gmail.com \
--cc=ian@airs.com \
--cc=overseers@gcc.gnu.org \
--cc=qneill@sourceware.org \
--cc=sebpop@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).