From: Ian Lance Taylor <ian@airs.com>
To: Christophe Lyon <christophe.lyon@linaro.org>, christophe.lyon@gmail.com
Cc: overseers@gcc.gnu.org,
Ramana Radhakrishnan <ramana.radhakrishnan@linaro.org>,
ramana.radhakrishnan@arm.com
Subject: Re: Write access request to the GCC repository
Date: Tue, 04 Sep 2012 04:44:00 -0000 [thread overview]
Message-ID: <m31uiipfbg.fsf@pepe.airs.com> (raw)
In-Reply-To: <CAKdteObZOw8uULN2wUNCjrsBdXTZzW3WKiCeMvOPgmXHGA16pw@mail.gmail.com> (Christophe Lyon's message of "Mon, 3 Sep 2012 18:22:23 +0200")
Christophe Lyon <christophe.lyon@linaro.org> writes:
> I'd like to be granted write access to the GCC repository; I already
> have an account on sourceware: clyon, which I used for contributions
> to GDB and Binutils.
>
> My sponsor is Ramana Radhakrishnan, who is one of the maintainers for ARM.
I've added you to the gcc group.
Ian
prev parent reply other threads:[~2012-09-04 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 16:23 Christophe Lyon
2012-09-04 4:44 ` Ian Lance Taylor [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=m31uiipfbg.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=christophe.lyon@gmail.com \
--cc=christophe.lyon@linaro.org \
--cc=overseers@gcc.gnu.org \
--cc=ramana.radhakrishnan@arm.com \
--cc=ramana.radhakrishnan@linaro.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).