On 5/9/20 12:31 PM, Arseny Solokha wrote: > I'd also like to nominate the following two: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52927 > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60158 > > which I also cannot close myself. There won't be any further revisions of this > list by me.
They affect given older versions, so if you just close them, that would imply that the bug in question in gcc-4.5.3 has been dealt with - which I assume is not the case. So, again, I'm not sure what you gain by closing these bugs. Having them marked as open means that someone has observed the issue with a certain gcc version and target. Moving it to "closed" just expresses that some people don't care about this bug anymore. But it doesn't change the fact that the bug still exists. The only thing you gain by closing such bugs is that you are reducing the number of open bug reports and you can somehow claim you fixed a bug. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
