public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: How to play flac files?
Date: Thu, 5 Oct 2006 04:27:13 +0000 (UTC)	[thread overview]
Message-ID: <eg21j1$n0p$4@sea.gmane.org> (raw)
In-Reply-To: 1160018216.12546.1.camel@scarlatti.leonora.org

"Vladimir G. Ivanovic" <vgivanovic@comcast.net> posted
1160018216.12546.1.camel@scarlatti.leonora.org, excerpted below, on  Wed,
04 Oct 2006 20:16:56 -0700:

> I don't know about you, but I don't look at headers like References. So,
> if the subject differ and the mailer says one is a reply to the other, I
> consider that a bug.

I don't normally look at them either, but my client of choice has an
option to thread by subject or by references, and I opt for and strongly
support its references threading feature.  If a post says it's a reply to
another post, that's what it is, even if the subject has changed.  If
someone's replying to a thread with something entirely unconnected (as in,
not natural thread drift, but an abrupt unconnected change), it's thread
hijacking and a "PEBKAC" (problem exists between keyboard and chair, IOW,
the human involved has a bug and he needs called on it so it can be
corrected).  Subject change on the same thread should be due to thread
drift, which is NOT thread hijacking and shouldn't be treated as such, by
separately threading it due only to the subject change.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-10-05  4:29 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             ` Duncan [this message]
2006-10-05  4:39             ` 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
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='eg21j1$n0p$4@sea.gmane.org' \
    --to=1i5t5.duncan@cox.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