From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Ian Lance Taylor <iant@google.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: when (not) use bugzilla for GCC?
Date: Mon, 26 Oct 2009 20:46:00 -0000 [thread overview]
Message-ID: <4AE5FF28.1050009@starynkevitch.net> (raw)
In-Reply-To: <mcrfx96s1b9.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
Ian Lance Taylor wrote:
> Basile STARYNKEVITCH <basile@starynkevitch.net> writes:
>
>> Did I understand correctly that GCC bugzilla treats magically the
>> *@gcc.gnu.org email adresses matching accounts usable for SVN write
>> access? This is great news!
>
> Yes, that is how it works.
May I respectfully suggest to the person maintaining the bugzilla a
notice in the login page saying something like:
GCC maintainers having write after approval (or better) access to the
GCC trunk should preferably login with their XXXXX@gcc.gnu.org email
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
next prev parent reply other threads:[~2009-10-26 19:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 18:48 Basile STARYNKEVITCH
2009-10-26 7:11 ` Joseph S. Myers
2009-10-26 11:57 ` Basile STARYNKEVITCH
2009-10-26 14:39 ` Ian Lance Taylor
2009-10-26 14:41 ` Richard Guenther
2009-10-26 14:56 ` Basile STARYNKEVITCH
2009-10-26 15:39 ` Richard Guenther
2009-10-29 5:35 ` Basile STARYNKEVITCH
2009-10-26 20:46 ` Basile STARYNKEVITCH [this message]
2009-10-26 21:42 ` Ian Lance Taylor
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=4AE5FF28.1050009@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=joseph@codesourcery.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).