This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Web: Making GNATS fixes a release criterion
- To: martin at loewis dot home dot cs dot tu-berlin dot de
- Subject: Re: Web: Making GNATS fixes a release criterion
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Mon, 01 May 2000 09:01:54 -0700
- Cc: gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <200004262123.XAA02487@loewis.home.cs.tu-berlin.de><20000429182551K.mitchell@codesourcery.com><200005011124.NAA07771@loewis.home.cs.tu-berlin.de>
>>>>> "Martin" == Martin v Loewis <martin@loewis.home.cs.tu-berlin.de> writes:
>> Martin, I hope you're willing to tackle the above chores. Your
>> assistance would be much appreciated.
Martin> I have just installed two new pages on gcc.gnu.org, namely
Martin> http://gcc.gnu.org/gnats.html
Martin> http://gcc.gnu.org/gnatswrite.html
Good, thanks! Is there any way to actually prevent people from
entering high-priority bugs, or is simply notifying people that
they're not supposed to do this the best we can do? For example, can
we make gccbug.el not allow high as a valid priority? Or make the
server disallow these entries from non-maintainers?
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com