https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84167
--- Comment #2 from rguenther at suse dot de <rguenther at suse dot de> --- On February 1, 2018 8:05:26 PM GMT+01:00, LpSolit at netscape dot net <gcc-bugzi...@gcc.gnu.org> wrote: >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84167 > >Frédéric Buclin <LpSolit at netscape dot net> changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |WORKSFORME > >--- Comment #1 from Frédéric Buclin <LpSolit at netscape dot net> --- >(In reply to Richard Biener from comment #0) >> I'm currently using the web gcc-bug mailinglist archive to cycle >through all >> new bugs each morning. > >Instead of doing this, you should click the "Bugs reported in the last >24 >hours" link on the Bugzilla home page. This will generate a list, and >the >Prev/Next link will automatically appear on each bug page. That does not work reliably in case there are more than 24 hours between invocations or when you just want to poll 'next'. I guess I'll try to look into doing some Greasemonkey script hacking then...
