From: "Frédéric Buclin" <LpSolit@netscape.net>
To: Sebastien Bourdeauducq <sebastien@milkymist.org>
Cc: Ian Lance Taylor <ian@airs.com>,
overseers@gcc.gnu.org, green@moxielogic.com
Subject: Re: Bug database write permissions
Date: Tue, 01 Feb 2011 20:14:00 -0000 [thread overview]
Message-ID: <4D4869B4.30203@netscape.net> (raw)
In-Reply-To: <1296588993.15319.41.camel@localhost.localdomain>
> I just submitted the form at
> http://sourceware.org/cgi-bin/pdw/ps_form.cgi (as specified on
> http://gcc.gnu.org/svnwrite.html) and got back an email with GCC
> Bugzilla credentials that were supposed to have write permissions into
> the bug database (copied below).
Yeah, I just updated the broken script. Should work like a charm, now. :)
Frédéric
prev parent reply other threads:[~2011-02-01 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110130180606.26118.qmail@sourceware.org>
2011-02-01 13:38 ` Sebastien Bourdeauducq
2011-02-01 14:23 ` Ian Lance Taylor
2011-02-01 18:00 ` Frédéric Buclin
2011-02-01 19:11 ` Sebastien Bourdeauducq
2011-02-01 19:25 ` Frédéric Buclin
2011-02-01 19:50 ` Sebastien Bourdeauducq
2011-02-01 20:14 ` Frédéric Buclin [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=4D4869B4.30203@netscape.net \
--to=lpsolit@netscape.net \
--cc=green@moxielogic.com \
--cc=ian@airs.com \
--cc=overseers@gcc.gnu.org \
--cc=sebastien@milkymist.org \
/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).