From: Ian Lance Taylor <iant@google.com>
To: jon@beniston.com
Cc: overseers@gcc.gnu.org, rth@redhat.com
Subject: Re: GCC SVN write access request
Date: Mon, 09 Nov 2009 15:12:00 -0000 [thread overview]
Message-ID: <mcrmy2vravo.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
From: Jon Beniston" <jon at beniston dot com>:
> I would like write access to the GCC repository so I can the Mico32 port
> (which Richard has approved.). I should already have an account on
> sourceware.org, under the username jbeniston.
Done.
Sorry for the delay.
Ian
next reply other threads:[~2009-11-09 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 15:12 Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-31 15:55 Jon Beniston
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=mcrmy2vravo.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=jon@beniston.com \
--cc=overseers@gcc.gnu.org \
--cc=rth@redhat.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).