This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Assigning priorities to GNATS reports
- From: Joe Buck <jbuck at synopsys dot com>
- To: mark at codesourcery dot com (Mark Mitchell)
- Cc: reichelt at igpm dot rwth-aachen dot de (Volker Reichelt), Joe dot Buck at synopsys dot COM (jbuck at synopsys dot com), bangerth at ticam dot utexas dot edu (bangerth at ticam dot utexas dot edu), gcc at gcc dot gnu dot org (gcc at gcc dot gnu dot org)
- Date: Fri, 15 Nov 2002 09:16:55 -0800 (PST)
- Subject: Re: Assigning priorities to GNATS reports
> > How about the following:
> >
> > [<branch-to-fix> regression (<branch-first>-<branch-last>)]
>
> I don't have any objection to this (the first part is the information
> I usually want most), but it seems a bit unwieldy to me. If, however,
> people think we can maintain that, it's fine by me!
I think it would be fine to list only <branch-to-fix> in the synopsis
(preferably in a rigidly consistent form, so we can put regular
expressions in our GNATS advanced queries). We need the latter
info as well, but it could appear in the body of the report somewhere
(or even in the audit trail, as it will tend to change).