From: Russ Dill <Russ.Dill@asu.edu>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Cc: David Woodhouse <postmaster@infradead.org>
Subject: Re: List etiquette.
Date: 23 Apr 2003 13:51:05 -0700 [thread overview]
Message-ID: <1051131065.1476.88.camel@russ.local> (raw)
In-Reply-To: <20030423204037.GB26678@wohnheim.fh-wedel.de>
On Wed, 2003-04-23 at 13:40, Jörn Engel wrote:
> On Wed, 23 April 2003 10:15:56 +0100, David Woodhouse wrote:
> >
> > Please ensure that you do not try to start a new thread
> > by just replying to an existing list message and changing the subject,
> > for similar reasons.
>
> Why exactly? I kind of like the habit of changing the subject in the
> middle of a thread where appropriate, like "foo (was: bar)".
He doesn't mean a topic change like, "There is a bug in tool foo blah
blah blah" "I like that tool, but I use tool bar blah blah blah" "(New
subject) did you know how to do x in tool bar?"
He means "I have an oops when I use foo with bar" "(reply) Where can I
find the latest CVS snapshot?"
Lazy people, not sensible topic shifting
next prev parent reply other threads:[~2003-04-23 20:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 9:15 List etiquette David Woodhouse
2003-04-23 9:40 ` David Woodhouse
2003-04-23 20:40 ` Jörn Engel
2003-04-23 20:51 ` Russ Dill [this message]
2003-04-23 21:05 ` Jörn Engel
2003-04-24 14:47 ` Grant Edwards
2003-04-24 15:20 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 2:59 David Antliff
2016-06-06 8:53 list etiquette Tobin Harding
2016-06-06 8:56 ` Robert P. J. Day
2016-06-06 14:56 ` Anuz Pratap Singh Tomar
2016-06-07 16:03 ` Frank Ch. Eigler
2016-06-11 10:47 ` Tobin Harding
2016-06-11 11:42 ` Anuz Pratap Singh Tomar
2016-06-12 9:58 ` Manavendra Nath Manav
2016-06-07 17:40 ` mhornung.linux at gmail.com
2016-06-07 18:17 ` Carlo Caione
2019-07-19 7:32 List etiquette Stephen Rothwell
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=1051131065.1476.88.camel@russ.local \
--to=russ.dill@asu.edu \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.