From: Ian Lance Taylor <ian@airs.com>
To: Tony Poppleton <tony.poppleton@gmail.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Bugzilla permissions
Date: Mon, 31 Jan 2011 18:55:00 -0000 [thread overview]
Message-ID: <m3ei7shpi8.fsf@pepe.airs.com> (raw)
In-Reply-To: <AANLkTi==P=tnb5fxqY5zNuhG6GeQy7Ls9s0jGrO0qiYY@mail.gmail.com> (Tony Poppleton's message of "Mon, 31 Jan 2011 12:19:58 +0000")
Tony Poppleton <tony.poppleton@gmail.com> writes:
> I wrote to this list a while ago requesting bugzilla permissions. Ian
> Lance Taylor kindly suggested I get a gnu account, which sounded like
> a great plan. However from discussions on the IRC chat, it seems that
> you need to get a sponsor, and a sponsor generally requires that you
> have proven yourself first by submitting some good patches to the
> project.
>
> Given that my main contribution was going to be bug triage in
> bugzilla, rather than patches, I am in a kind of catch 22 on getting a
> gnu account. I also don't need the SVN write access.
>
> Richard Guenther suggested an easier route would just be to get the
> required bugzilla permissions, and that I should contact the bugzilla
> maintainer to do so.
>
> How do I go about contacting the bugzilla maintainer?
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
next prev parent reply other threads:[~2011-01-31 18:55 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 [this message]
2011-01-31 20:19 ` Tony Poppleton
2011-02-01 6:28 ` Ian Lance Taylor
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=m3ei7shpi8.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).