From: "Jörn Engel" <joern@logfs.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: "Jörn Engel" <joern@logfs.org>,
"Linux mtd" <linux-mtd@lists.infradead.org>
Subject: Re: Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ?
Date: Fri, 23 Nov 2007 13:46:58 +0100 [thread overview]
Message-ID: <20071123124658.GA1239@lazybastard.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711230836240.523@lnxricardw.se.axis.com>
On Fri, 23 November 2007 08:42:16 +0100, Ricard Wanderlof wrote:
> On Thu, 22 Nov 2007, Jörn Engel wrote:
>
> > Please don't reply to the list only. If you are asking me a question,
> > it is really impolite to send it elsewhere. And I bet others would like
> > to stay on Cc: as well.
>
> Sorry, no harm intended. (I tend to view discussions on a mailing list as
> being on the mailing list, not between a couple of people with a cc to the
> mailing list, because other people on the list should feel they can
> respond to the questions posed. But either way is fine with me).
Some discussions are on several mailing lists. Some people like me
regularly read about a dozen mailing lists. Linux-kernel alone accounts
for nearly 400 mails a day. Some people "read" mailing lists with the
'D' key and only occasionally stop when spotting something interesting.
Since I moved to my own server about a year ago, I received 1.3GB of
mail, not counting spam.
The only reasonably sane strategy I know is to simply reply to all and
not worry about the size of the Cc: list. If the discussion was private
before, it remains private. If it was public, it remains public.
Jörn
--
If you're willing to restrict the flexibility of your approach,
you can almost always do something better.
-- John Carmack
next prev parent reply other threads:[~2007-11-23 12:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 14:27 Some news for this: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD ? Gregory CLEMENT
2007-11-21 16:08 ` Jörn Engel
2007-11-21 16:28 ` Gregory CLEMENT
2007-11-21 16:58 ` Josh Boyer
2007-11-21 17:07 ` Gregory CLEMENT
2007-11-21 17:13 ` Josh Boyer
2007-11-21 17:15 ` Jörn Engel
2007-11-21 17:32 ` Gregory CLEMENT
2007-11-21 17:43 ` Vitaly Wool
2007-11-21 17:45 ` Jörn Engel
2007-11-21 17:56 ` Vitaly Wool
2007-11-21 18:04 ` Jörn Engel
2007-11-23 14:35 ` Gregory CLEMENT
2007-11-23 14:45 ` Jörn Engel
2007-11-23 15:06 ` Gregory CLEMENT
2007-11-21 20:46 ` Ricard Wanderlof
2007-11-21 21:32 ` Jörn Engel
2007-11-21 22:33 ` Gregory CLEMENT
2007-11-21 22:54 ` Jörn Engel
2007-11-22 7:58 ` Ricard Wanderlof
2007-11-22 13:26 ` Jörn Engel
2007-11-23 7:42 ` Ricard Wanderlof
2007-11-23 8:18 ` Artem Bityutskiy
2007-11-23 9:08 ` Ricard Wanderlof
2007-11-23 9:21 ` Artem Bityutskiy
2007-11-23 9:28 ` Ricard Wanderlof
2007-11-23 18:40 ` David Brown
2007-11-26 9:42 ` Ricard Wanderlof
2007-11-26 13:58 ` Claudio Lanconelli
2007-11-23 8:19 ` Artem Bityutskiy
2007-11-23 12:46 ` Jörn Engel [this message]
2007-11-22 7:58 ` Ricard Wanderlof
2007-11-22 13:08 ` Jamie Lokier
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=20071123124658.GA1239@lazybastard.org \
--to=joern@logfs.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.com \
/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