Bugs for 5/21
Dara Hazeghi
dhazeghi@yahoo.com
Thu May 22 04:37:00 GMT 2003
Hello,
Hello,
well it's good to see bugzilla is in action today. I'm a bit concerned
that with the list cced on every report, it's going to become
unreadable, but I'll leave that to the experts. Currently the biggest
problem I see is the status of a large number of bugs as unconfirmed.
I'd like to try and get that number reduced significantly. The other
thing I'd like to do is get the host/target triplets correctly
specified, to simplify searching for bugs. To make matters easier, I
was wondering whether I could be given some sort of bugzilla write
access, enough to change the statuses, and update the summaries, hosts
and other fields. I would still defer other's judgment with regard to
closing reports however. Does this sound feasible? Thanks,
Dara
Unconfirmed->Wait
10895
10806
10620
10848
8710
change to ->Verified
10903
10899
10890 3.3 and 3.4 regression building chunk of linux kernel. Maybe this
should be high priority?
10249
9571
9337
8812
7577
7003
Other
10884 duplicate of 10890
10898 attachment should be copied to 10897, and 10898 should be closed
10905 empty
10906 information should be appended to 10897, and 10906 should be
closed
10909 empty
10912 empty
Suggestions?
3985 Are we allowed to put things in "wait" to find out from developers
whether bugs are still present? Granted it's unusual, but some of these
are _really_ old.
More information about the Gcc-bugs
mailing list