This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Bug Digest 5/24
- From: Dara Hazeghi <dhazeghi at yahoo dot com>
- To: gcc-bugs at gcc dot gnu dot org
- Cc: Giovanni Bajo <giovannibajo at libero dot it>
- Date: Sun, 25 May 2003 00:55:32 -0700
- Subject: Bug Digest 5/24
Hello,
I have a few general suggestions/questions.
gcc-bugs is still being flooded. I really think we need to come up with
2 lists. One for new bugs and questions, one for followups on bugzilla.
what is the policy regarding assigned? Is it reasonable to assign
target-specific bugs to their respective port maintainers? The webpage
(http://gcc.gnu.org/bugs/management.html) doesn't indicate.
Are 3.3 bugs which are not regressions, and have been fixed on 3.4,
allowed to be closed? This also isn't clear (though I may not have
looked in the right places).
Thanks,
Dara
P.S. Here's the list. Many thanks to Andrew Pinski for taking care of
most of it (so the list is quite small). When going through, I included
bugs which other people have updated and seem in need of STATUS change.
Wait
3845
5119
6066
7054
7055
7979
9710
10274
10605
New
10968
10936
10851
10775
10700
10692 (I'm assuming the summary is correct)
10681
10587 (or feedback, though I don't think the info. is quite that
critical)
10467
10413
9596
7078 (Wolfgang is this still present?)
7013
6882
6851
6717
6588
6452 (also a duplicate as noted, perhaps close in favor of the other
report?)
6065
5910
5903
5178
5135
4914
4720
4478
3746
Resolved
10848
10806
7555
6767
6115
5256
Other
9787? not sure where this fits. Maybe WAIT, or ...?