This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: your RESOLVED->CLOSED changes
- From: Nathanael Nerode <neroden at twcny dot rr dot com>
- To: Daniel Berlin <dberlin at dberlin dot org>, gcc at gcc dot gnu dot org
- Date: Fri, 23 May 2003 11:50:30 -0400
- Subject: Re: your RESOLVED->CLOSED changes
- References: <2879483D-8D2F-11D7-B31E-000A95A34564@dberlin.org>
Daniel Berlin wrote:
Because it gets mail when you close/resolve bugs, and when you add
Given the presence of 'closed' *and* 'resolved' states, this is
redundant, sadly. :-/
However, admins can always do it another few ways that you can't:
The trivial way is to edit the gcc-bugs user to have a known password
(it's a random string of characters so that nobody screws with it),
which requires admin privileges, log in as gcc-bugs, and make the batch
changes from gcc-bugs.
gcc-bugs won't get mail about it's own changes (it's a preference, so it
can be changed, but shouldn't).
Cute. :-)