https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
--- Comment #10 from Paolo Carlini ---
In my opinion we should *always* set it when closing bugs: many, many, users
complain that isn't always clear which is the first release where a bug is
fixed. Actually, we should also spend more time on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
--- Comment #9 from Eric Gallager ---
(In reply to Paolo Carlini from comment #8)
> In any case, please always set the Target Milestone when closing a bug.
I thought that was just for regressions...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
Paolo Carlini changed:
What|Removed |Added
Target Milestone|--- |8.0
--- Comment #8 from Paolo Carlini
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
Eric Gallager changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
--- Comment #6 from Paolo Carlini ---
See Comment 4: why 2 errors?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
vegard.nossum at gmail dot com changed:
What|Removed |Added
CC||vegard.nossum at oracle
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
Paolo Carlini changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
Martin Liška changed:
What|Removed |Added
Keywords||ice-on-invalid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
--- Comment #2 from Eric Gallager ---
*** Bug 81839 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81837
--- Comment #1 from Eric Gallager ---
*** Bug 81838 has been marked as a duplicate of this bug. ***
10 matches
Mail list logo