public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/45818] Missing message-ids in Bugzilla messages
Date: Tue, 28 Sep 2010 19:55:00 -0000	[thread overview]
Message-ID: <20100928195500.8NQ51dZFRgPx82_3-gVwu-a7TDePtkNgXO4GIiuYVDk@z> (raw)
In-Reply-To: <bug-45818-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45818

Frédéric Buclin <LpSolit at netscape dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2010.09.28 16:37:28
               date|                            |
     Ever Confirmed|0                           |1

--- Comment #1 from Frédéric Buclin <LpSolit at netscape dot net> 2010-09-28 16:37:28 UTC ---
New bugs have e.g.:

Message-ID: <bug-45818-18765@http.gcc.gnu.org/bugzilla/>

And additional comments and changes have:

In-Reply-To: <bug-45818-18765@http.gcc.gnu.org/bugzilla/>
References: <bug-45818-18765@http.gcc.gnu.org/bugzilla/>

So you can still list bugs in threads correctly. But I agree that RFC 2822
recommends that *each* message has its own unique Message-ID, which we don't do
here. I will report the bug upstream.


  reply	other threads:[~2010-09-28 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 17:45 [Bug web/45818] New: " jsm28 at gcc dot gnu.org
2010-09-28 19:55 ` LpSolit at netscape dot net [this message]
2010-10-27  9:47 ` [Bug web/45818] " 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=20100928195500.8NQ51dZFRgPx82_3-gVwu-a7TDePtkNgXO4GIiuYVDk@z \
    --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: link
Be 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).