From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org, Nick Clifton <nickc@redhat.com>,
Tejas Belagod <Tejas.Belagod@arm.com>,
Richard Earnshaw <rearnsha@arm.com>
Subject: Re: Write permission to binutils.
Date: Mon, 27 Sep 2010 13:10:00 -0000 [thread overview]
Message-ID: <20100927130958.GC18236@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4CA09574.6000705@redhat.com>
On Mon, Sep 27, 2010 at 02:00:36PM +0100, Nick Clifton wrote:
>Hi Chris,
>
>>>> Wrong page, I think. Tejas already has a GCC account.
>>>
>>> This is for a sourceware account, which I did not know if Tejas already
>>> had. Anyway he has used the form and I have approved the request, so
>>> everything should be set up now.
>>
>> No, Richard was right. Quoting from that page:
>>
>> "Note that if you already have an account on sourceware.org or
>> gcc.gnu.org for CVS or Subversion write access, then do not use this
>> form. Instead send an email to the overseers mail account at this site
>> telling what project you want write access to and who approved that
>> access."
>
>Right - I saw that - but I did not know if Tejas already had a
>sourceware account, so I figured that by directing him to the
>account-request page he would read the caveat above and if necessary
>just email you directly. :-)
The email that you responded to, which went to overseers, said that he
already had a GCC account. If he has an account on gcc.gnu.org, he has
an an account on sourceware.org since they are the same machine. So,
he'd already done the right thing when you sent him to the web page.
cgf
prev parent reply other threads:[~2010-09-27 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <680044E4997F5343A2C58032DDD0991637DE5F@ZIPPY.Emea.Arm.com>
2010-09-27 12:23 ` Nick Clifton
2010-09-27 12:35 ` Richard Earnshaw
2010-09-27 12:48 ` Nick Clifton
2010-09-27 12:58 ` Christopher Faylor
2010-09-27 13:01 ` Nick Clifton
2010-09-27 13:10 ` Christopher Faylor [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=20100927130958.GC18236@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=Tejas.Belagod@arm.com \
--cc=nickc@redhat.com \
--cc=overseers@sourceware.org \
--cc=rearnsha@arm.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).