unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Don Armstrong <don@donarmstrong.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bug tracker breaks rmail-next-same-subject
Date: Fri, 12 Dec 2008 18:36:10 -0500	[thread overview]
Message-ID: <E1LBHYI-0002NS-Ie@fencepost.gnu.org> (raw)
In-Reply-To: <20081212232551.GJ24493@volo.donarmstrong.com> (message from Don Armstrong on Fri, 12 Dec 2008 15:25:51 -0800)

> Date: Fri, 12 Dec 2008 15:25:51 -0800
> From: Don Armstrong <don@donarmstrong.com>
> 
> > > That's why References: and In-Reply-To: exist.
> > 
> > You are evidently assuming that everybody uses MUA that preserve
> > these headers as they should. The reality is a bit different.
> 
> There are loads of broken MUAs; that doesn't change the fact that
> they're broken. References: and In-Reply-To: are the primary way of
> tracking threads. In the absence of them, you can try to track threads
> using subject, but that's never the first option.

I don't want to memorize two different ways of following a subject.  I
have things to do with my time other than read emacs-devel and
bug-gnu-emacs.  As long as there are loads of broken MUAs, using the
Subject line will always be more reliable than references.  Until now.

Btw, the bug tracker seems to keep only one reference in References:,
which doesn't help too much to follow a thread by that.

> If you want to follow a thread, References: and In-Reply-To: are the
> way to do that; Subject: may approximate it, but it's never as
> accurate.

What other use cases will break it?  Until now, I didn't see any.




  reply	other threads:[~2008-12-12 23:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 12:44 Bug tracker breaks rmail-next-same-subject Eli Zaretskii
2008-12-12 19:10 ` Stefan Monnier
2008-12-12 23:16   ` Eli Zaretskii
2008-12-12 21:47 ` Don Armstrong
2008-12-12 23:03   ` Eli Zaretskii
2008-12-12 23:25     ` Don Armstrong
2008-12-12 23:36       ` Eli Zaretskii [this message]
2008-12-12 23:57         ` Don Armstrong
2008-12-13  2:41           ` Eli Zaretskii
2008-12-13  9:42             ` Don Armstrong
2008-12-13 22:58               ` Glenn Morris
2008-12-13 23:14                 ` Bugs against emacsbugs.donarmstrong.com Don Armstrong
2008-12-13 23:33                   ` Glenn Morris
2008-12-14  0:23                     ` Don Armstrong
2008-12-14  3:51                       ` Stefan Monnier
2008-12-14  8:06                         ` Stephen J. Turnbull
2008-12-14 10:13                         ` Don Armstrong
2008-12-14 20:53                           ` Glenn Morris
2008-12-14 21:27                           ` Stefan Monnier
2008-12-17  5:39                             ` Don Armstrong
2008-12-17 16:10                               ` Stefan Monnier
2008-12-18  7:43                                 ` Don Armstrong
2008-12-18 21:46                                   ` Stefan Monnier
2008-12-14  8:14                       ` Stephen J. Turnbull
2008-12-14  2:50                     ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LBHYI-0002NS-Ie@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=don@donarmstrong.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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