public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug web/55954] New: Bugzilla breaks mail threading
@ 2013-01-12  3:42 mkuvyrkov at gcc dot gnu.org
  2013-01-12  4:59 ` [Bug web/55954] " pinskia at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: mkuvyrkov at gcc dot gnu.org @ 2013-01-12  3:42 UTC (permalink / raw)
  To: gcc-bugs


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

             Bug #: 55954
           Summary: Bugzilla breaks mail threading
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: web
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: mkuvyrkov@gcc.gnu.org


GCC bugzilla prepends "New: " to subject lines which causes popular mail
clients (Gmail, Apple Mail, Sparrow, likely others) to use different mail
threads for the original bug email and for followups.  This is annoying.

Mail clients usually put messages in the same thread if (1) subjects are the
same modulo "Re:" and (2) In-Reply-To header is set to a message from the
thread.  Using "New: " for the first message, but not followups, breaks this
model.

There ought to be a switch to disable this.

Thanks.


^ permalink raw reply	[flat|nested] 5+ messages in thread
* [Bug web/55954] Bugzilla breaks mail threading
  2013-01-12  3:42 [Bug web/55954] New: Bugzilla breaks mail threading mkuvyrkov at gcc dot gnu.org
@ 2013-01-12  4:59 ` pinskia at gcc dot gnu.org
  2013-01-12  5:07 ` pinskia at gcc dot gnu.org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu.org @ 2013-01-12  4:59 UTC (permalink / raw)
  To: gcc-bugs


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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-01-12 04:59:12 UTC ---
I think it is really a bug in the mail clients if they don't just use
In-Reply-To instead.


^ permalink raw reply	[flat|nested] 5+ messages in thread
* [Bug web/55954] Bugzilla breaks mail threading
  2013-01-12  3:42 [Bug web/55954] New: Bugzilla breaks mail threading mkuvyrkov at gcc dot gnu.org
  2013-01-12  4:59 ` [Bug web/55954] " pinskia at gcc dot gnu.org
@ 2013-01-12  5:07 ` pinskia at gcc dot gnu.org
  2013-01-12 14:50 ` redi at gcc dot gnu.org
  2013-01-14 13:19 ` rguenth at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu.org @ 2013-01-12  5:07 UTC (permalink / raw)
  To: gcc-bugs


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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> 2013-01-12 05:06:43 UTC ---
(In reply to comment #1)
> I think it is really a bug in the mail clients if they don't just use
> In-Reply-To instead.

The reason why I say that is because some mail clients other things than just
Re:.  Some use the native language version instead like AW or SV.  So again the
mail client is broken and we really should not be working around broken mail
clients if they cannot handle the case new is added to the subject.


^ permalink raw reply	[flat|nested] 5+ messages in thread
* [Bug web/55954] Bugzilla breaks mail threading
  2013-01-12  3:42 [Bug web/55954] New: Bugzilla breaks mail threading mkuvyrkov at gcc dot gnu.org
  2013-01-12  4:59 ` [Bug web/55954] " pinskia at gcc dot gnu.org
  2013-01-12  5:07 ` pinskia at gcc dot gnu.org
@ 2013-01-12 14:50 ` redi at gcc dot gnu.org
  2013-01-14 13:19 ` rguenth at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: redi at gcc dot gnu.org @ 2013-01-12 14:50 UTC (permalink / raw)
  To: gcc-bugs


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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-01-12 14:49:43 UTC ---
Without the "New" I can't keep track of new bugs at
http://gcc.gnu.org/ml/gcc-bugs/2013-01/ which is how I monitor and respond to
libstdc++ bugs.


^ permalink raw reply	[flat|nested] 5+ messages in thread
* [Bug web/55954] Bugzilla breaks mail threading
  2013-01-12  3:42 [Bug web/55954] New: Bugzilla breaks mail threading mkuvyrkov at gcc dot gnu.org
                   ` (2 preceding siblings ...)
  2013-01-12 14:50 ` redi at gcc dot gnu.org
@ 2013-01-14 13:19 ` rguenth at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu.org @ 2013-01-14 13:19 UTC (permalink / raw)
  To: gcc-bugs


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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-14 13:18:58 UTC ---
(In reply to comment #3)
> Without the "New" I can't keep track of new bugs at
> http://gcc.gnu.org/ml/gcc-bugs/2013-01/ which is how I monitor and respond to
> libstdc++ bugs.

Me too, I'd rather not lose "New:" markers.  Pretty please.

Thus -> WONTFIX.  It's a MUA error not to look at In-Reply-To.


^ permalink raw reply	[flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-01-14 13:19 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-12  3:42 [Bug web/55954] New: Bugzilla breaks mail threading mkuvyrkov at gcc dot gnu.org
2013-01-12  4:59 ` [Bug web/55954] " pinskia at gcc dot gnu.org
2013-01-12  5:07 ` pinskia at gcc dot gnu.org
2013-01-12 14:50 ` redi at gcc dot gnu.org
2013-01-14 13:19 ` rguenth at gcc dot gnu.org

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).