From: Ian Lance Taylor <ian@airs.com>
To: Stafford Horne <shorne@gmail.com>
Cc: overseers@gcc.gnu.org, Jeff Law <law@redhat.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: Request write after approval
Date: Sun, 04 Nov 2018 04:16:00 -0000 [thread overview]
Message-ID: <m3va5dqy0z.fsf@pepe.airs.com> (raw)
In-Reply-To: <20181103060454.GK2843@lianli.shorne-pla.net> (Stafford Horne's message of "Sat, 3 Nov 2018 15:04:54 +0900")
Stafford Horne <shorne@gmail.com> writes:
> Could you please entitle me (shorne) for write after approval for GCC? I
> believe I have SSH access already as I am able to log in and checkout gcc vs
> svn.
>
> I am listing Jeff Law and Segher Boessenkool as my sponsors as they have been
> very helpful with my patches so far. I hope that is alright.
Jeff, Segher, OK?
Ian
next prev parent reply other threads:[~2018-11-04 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 6:05 Stafford Horne
2018-11-04 4:16 ` Ian Lance Taylor [this message]
2018-11-04 4:26 ` Jeff Law
2018-11-04 4:34 ` Ian Lance Taylor
2018-11-04 9:09 ` Stafford Horne
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=m3va5dqy0z.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=law@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=shorne@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).