This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: when (not) use bugzilla for GCC?

From: Ian Lance Taylor <iant at google dot com>
To: Basile STARYNKEVITCH <basile at starynkevitch dot net>
Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>
Date: Mon, 26 Oct 2009 13:23:04 -0700
Subject: Re: when (not) use bugzilla for GCC?
References: <4AE4998D.7040608@starynkevitch.net> <Pine.LNX.4.64.0910260154480.3671@digraph.polyomino.org.uk> <4AE54B94.3090708@starynkevitch.net> <mcrfx96s1b9.fsf@dhcp-172-17-9-151.mtv.corp.google.com> <4AE5FF28.1050009@starynkevitch.net>

Basile STARYNKEVITCH <basile@starynkevitch.net> writes:

> 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

Good idea, but nobody maintains bugzilla these days, at least beyond
the bare minimum of taking a look if something breaks.  If anybody
wants to tackle this and knows what to do, let me know.

Ian

References:
- when (not) use bugzilla for GCC?
  - From: Basile STARYNKEVITCH
- Re: when (not) use bugzilla for GCC?
  - From: Joseph S. Myers
- Re: when (not) use bugzilla for GCC?
  - From: Basile STARYNKEVITCH
- Re: when (not) use bugzilla for GCC?
  - From: Ian Lance Taylor
- Re: when (not) use bugzilla for GCC?
  - From: Basile STARYNKEVITCH

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]