From: James Bowman <james.bowman@ftdichip.com>
To: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Cc: Jeff Law <law@redhat.com>
Subject: Request write access to GCC
Date: Fri, 15 May 2015 21:04:00 -0000 [thread overview]
Message-ID: <CA9BBF0458F83C4F9051448B941B57D117BA028B@glaexch3> (raw)
Hello,
I have an existing account
jamesbowman@sourceware.org
And I am requesting "write after approval" access to the GCC project. My sponsor is
Jeff Law [law@redhat.com]
Thanks very much.
--
James Bowman
FTDI Open Source Liaison
next reply other threads:[~2015-05-15 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 21:04 James Bowman [this message]
2015-05-16 4:35 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2009-12-04 1:49 Request write access to gcc Shujing Zhao
2009-12-04 5:51 ` Ian Lance Taylor
2009-12-07 11:02 ` Shujing Zhao
2009-12-07 18:34 ` Ian Lance Taylor
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=CA9BBF0458F83C4F9051448B941B57D117BA028B@glaexch3 \
--to=james.bowman@ftdichip.com \
--cc=law@redhat.com \
--cc=overseers@gcc.gnu.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).