From: Ian Lance Taylor <ian@airs.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Roland McGrath <roland@hack.frob.com>,
overseers@sourceware.org, Diego Novillo <dnovillo@google.com>
Subject: Re: add roland to gcc group
Date: Fri, 16 Nov 2012 06:12:00 -0000 [thread overview]
Message-ID: <m3wqxnfxqz.fsf@pepe.airs.com> (raw)
In-Reply-To: <20121115013310.GA8582@redhat.com> (Frank Ch. Eigler's message of "Wed, 14 Nov 2012 20:33:10 -0500")
"Frank Ch. Eigler" <fche@redhat.com> writes:
> Hi -
>
>> I'd like to be in the write-after-approval club. [...]
>
> Welcome to the club.
Please add yourself to the write-after-approval list in the GCC
MAINTAINERS file. The GCC project tracks the people with write access.
Thanks.
Ian
prev parent reply other threads:[~2012-11-15 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 0:49 Roland McGrath
2012-11-15 0:56 ` Andrew Pinski
2012-11-15 1:42 ` Frank Ch. Eigler
2012-11-16 6:12 ` 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=m3wqxnfxqz.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=dnovillo@google.com \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=roland@hack.frob.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).