public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/113190] Alert not to report bugs against EOL releases Date: Wed, 03 Jan 2024 01:55:47 +0000 [thread overview] Message-ID: <bug-113190-4-nNmSUkovp7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113190-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113190 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2024-01-03 Component|web |other Keywords| |documentation --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I had thought this was documented on https://gcc.gnu.org/bugs/ but I was wrong. We do have: ``` Duplicate bug reports, or reports of bugs already fixed in the development tree, especially those that have already been reported as fixed last week :-) ``` On https://gcc.gnu.org/bugs/ but that is more geared towards people using the trunk rather than releases.
next prev parent reply other threads:[~2024-01-03 1:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-01 14:55 [Bug web/113190] New: " xry111 at gcc dot gnu.org 2024-01-01 15:01 ` [Bug web/113190] " eyalroz1 at gmx dot com 2024-01-03 1:55 ` pinskia at gcc dot gnu.org [this message] 2024-01-08 14:24 ` [Bug other/113190] " rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113190-4-nNmSUkovp7@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).