From: "Vladimir G. Ivanovic" <vgivanovic@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: Thread-hijacking (was: Re: [gentoo-amd64] How to play flac files?)
Date: Wed, 04 Oct 2006 20:23:13 -0700 [thread overview]
Message-ID: <1160018593.12546.8.camel@scarlatti.leonora.org> (raw)
In-Reply-To: <200610041429.03312.bss03@volumehost.net>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
On Wed, 2006-10-04 at 14:28 -0500, Boyd Stephen Smith Jr. wrote:
> On Wednesday 04 October 2006 11:25, "Vladimir G. Ivanovic"
> <vgivanovic@comcast.net> wrote about 'Re: [gentoo-amd64] How to play flac
> files?':
> > Agreed, but my mail reader (Evolution) shows his subject to be "How to
> > play flac files?" which is a new subject. My mail reader shows Patric's
> > original email to be a sub-thread of a previous email with a different
> > subject, but I would say that this is a bug in Evolution, not that
> > hijacking has occurred.
>
> That's the very *definition* of highjacking. There's a specific header
> ('References', IIRC) that is used to indicate what thread a message is
> part of. This is for various reasons, but mostly because matching subject
> doesn't give you full information about the tree structure of the thread,
> and attempting to match quoted text can lead to madness.
>
> While some mail clients provide subject based threading, it is not the
> correct way to indicate a message is threaded. Subject-based threading is
> generally only useful to work around mail clients that do not properly add
> a 'References' header (or whatever header you are supposed to use, I don't
> remember, ATM).
>
About, oh, 99.9% of the world's email users wouldn't have any idea of
what we're talking about. The notion that emails with different subjects
would be part of the same thread would strike them as, expressing it
politely, interesting.
---- Vladimir
--
Vladimir G. Ivanovic <vgivanovic@comcast.net>
[-- Attachment #2: Type: text/html, Size: 2537 bytes --]
next prev parent reply other threads:[~2006-10-05 3:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 8:46 [gentoo-amd64] musicbrainz Paul Stear
2006-10-03 11:23 ` Adam James
2006-10-03 19:43 ` Boyd Stephen Smith Jr.
2006-10-04 8:11 ` [gentoo-amd64] How to play flac files? Patric Douhane
2006-10-04 8:49 ` Daniel Iliev
2006-10-04 16:25 ` Vladimir G. Ivanovic
2006-10-04 16:32 ` Bo Ørsted Andresen
2006-10-05 3:16 ` Vladimir G. Ivanovic
2006-10-05 4:27 ` [gentoo-amd64] " Duncan
2006-10-05 4:39 ` [gentoo-amd64] " Boyd Stephen Smith Jr.
2006-10-05 12:35 ` Hemmann, Volker Armin
2006-10-04 19:28 ` Thread-hijacking (was: Re: [gentoo-amd64] How to play flac files?) Boyd Stephen Smith Jr.
2006-10-05 3:23 ` Vladimir G. Ivanovic [this message]
2006-10-05 4:45 ` Boyd Stephen Smith Jr.
2006-10-06 4:21 ` Richard Fish
2006-10-06 13:30 ` [gentoo-amd64] Re: Thread-hijacking Richard Freeman
2006-10-06 23:02 ` Conway S. Smith
2006-10-07 1:27 ` Richard Freeman
2006-10-08 3:05 ` [gentoo-amd64] Sylpheed-claws GPG & S/MIME support (was: Re: Thread-hijacking) Conway S. Smith
2006-10-08 16:17 ` [gentoo-amd64] Sylpheed-claws GPG & S/MIME support Richard Freeman
2006-10-08 16:21 ` Richard Freeman
2006-10-05 9:38 ` [gentoo-amd64] How to play flac files? Paul Stear
2006-10-05 13:49 ` [gentoo-amd64] " Duncan
2006-10-07 8:02 ` [gentoo-amd64] " Pawel Kraszewski
2006-10-04 8:55 ` Conway S. Smith
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=1160018593.12546.8.camel@scarlatti.leonora.org \
--to=vgivanovic@comcast.net \
--cc=gentoo-amd64@lists.gentoo.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