From: Ian Lance Taylor <ian@airs.com>
To: Tony Poppleton <tony.poppleton@gmail.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Bugzilla permissions
Date: Tue, 01 Feb 2011 06:28:00 -0000 [thread overview]
Message-ID: <m3tygofeuj.fsf@pepe.airs.com> (raw)
In-Reply-To: <AANLkTik0N6YP77r9-UKUgis=M4FRv5_q-icmWJxJNg01@mail.gmail.com> (Tony Poppleton's message of "Mon, 31 Jan 2011 20:18:44 +0000")
Tony Poppleton <tony.poppleton@gmail.com> writes:
>> Sorry for the confusion which I accidentally instigated. As I said in a
>> note I just sent to gcc@gcc.gnu.org, you should get a gcc maintainer to
>> sponsor you for bugzilla changes.
>>
>> Thanks for your interest in gcc.
>>
>> Ian
>>
>
> Thanks Ian, no need to apologize; you and Richard have both been very
> helpful in getting me started.
>
> However as an outsider to all the main contributing companies, I don't
> see how I can get any of the gcc maintainers to sponsor me -
> especially given the non-standard QA role I am trying to perform (i.e.
> rather than a standard patch-submitting developer role).
>
> I will ponder how to proceed.
I went back and saw the message you sent to gcc@gcc.gnu.org earlier this
month. It seems reasonable. I went ahead and gave you bugzilla
privileges. Please don't abuse them. Thanks for your interest, and
sorry again for the confusion.
Ian
next prev parent reply other threads:[~2011-02-01 6:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 20:01 Tony Poppleton
2011-01-26 5:05 ` Ian Lance Taylor
2011-01-26 6:54 ` Tony Poppleton
2011-01-26 14:10 ` Ian Lance Taylor
2011-01-31 12:20 ` Tony Poppleton
2011-01-31 18:55 ` Ian Lance Taylor
2011-01-31 20:19 ` Tony Poppleton
2011-02-01 6:28 ` Ian Lance Taylor [this message]
2011-02-01 7:06 ` Tony Poppleton
2016-05-20 1:47 Cary Coutant
2016-05-20 1:50 ` Frank Ch. Eigler
2016-05-20 2:03 ` Cary Coutant
2016-05-20 2:10 Cary Coutant
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=m3tygofeuj.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=overseers@gcc.gnu.org \
--cc=tony.poppleton@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).