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: Bugzilla



On Tuesday, February 25, 2003, at 04:00 AM, Nathanael Nerode wrote:


 (Am I wrong?)  What will happen
to the exceedingly useful 'class'?

I can throw it into the keywords field automatically if you like, but
it'll be a few days to get it right.

That would be fine. Some suggestions on the keyword conversion:


* wrong-code, ice-on-legal-code, ice-on-illegal-code, rejects-legal, and
accepts-illegal should become keywords. This information *needs* to be
kept, not dropped.


Done (They'll appear later today when i do a database update)
* pessimizes-code should probably become a keyword too, though I couuld
be convinced otherwise.

Done.

* sw-bug should be dropped; it's the catch-all category for
unclassified PRs.

Dropped.
* duplicate should really map to whatever Bugzilla uses for duplicate
tracking.

It is already:
if (defined($pr_data{"Class"}) && $pr_data{"Class"} =~ /^duplicate/o) {
$resolution = "DUPLICATE";
} elsif (defined($pr_data{"Class"}) && $pr_data{"Class"} =~ /^mistaken/o) {
$resolution = "INVALID";
....



* doc-bug could map to a 'documentation' component, or be a keyword; I'm
not sure which would be better.



* change-request should map to a severity, I believe.


It is already (it's mapped to severity "enhancement").


I accidently did a case sensitive grep for class when i said we ignore class completely.
The above cases are, however, the only previous uses until now (duplicate/mistaken/enhancement).


--Dan


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