public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug web/45818] New: Missing message-ids in Bugzilla messages Date: Tue, 28 Sep 2010 17:45:00 -0000 [thread overview] Message-ID: <bug-45818-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45818 Summary: Missing message-ids in Bugzilla messages Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: web AssignedTo: unassigned@gcc.gnu.org ReportedBy: jsm28@gcc.gnu.org CC: LpSolit@netscape.net It appears that messages generated by the new Bugzilla only have a Message-ID header if they are messages for new bugs, not for comments. This breaks at least the "Raw text" links in the gcc-bugs list archives. I don't think it matters much what the message-ids are as long as they are unique, but Bugzilla should generate them rather than leaving this to some downstream MTA.
next reply other threads:[~2010-09-28 15:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-28 17:45 jsm28 at gcc dot gnu.org [this message] 2010-09-28 19:55 ` [Bug web/45818] " LpSolit at netscape dot net 2010-10-27 9:47 ` LpSolit at netscape dot net 2010-11-03 16:19 ` LpSolit at netscape dot net
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-45818-4@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).