From: Paul Jackson <pj@sgi.com>
To: Andrew Buehler <abuehler.kernel@gmail.com>
Cc: stern@rowland.harvard.edu, oliver.pntr@gmail.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
greg@kroah.com, linux-scsi@vger.kernel.org,
linux-usb@vger.kernel.org, Joseph Fannin <jfannin@gmail.com>
Subject: Re: USB regression (and other failures) in 2.6.2[45]*
Date: Sun, 17 Feb 2008 01:20:06 -0600 [thread overview]
Message-ID: <20080217012006.3757dfae.pj@sgi.com> (raw)
In-Reply-To: <47B71372.5050804@gmail.com>
Andrew wrote:
> (Note: I consider it blatantly incorrect to send a reply both to a
> mailing list and directly to the address of someone who is subscribed to
> that list
Regardless of how you consider it, that is how responding to these big
lists -must- work.
There is no practical way for respondents to know, without spending at
a minimum several minutes of their time per reply, whether or not the
explicit receipients of a message are or are not also on one or more of
the receiving lists.
Do you really expect, Andrew, that I should examine the membership lists
of each of linux-scsi, linux-usb and linux-kernel (if they are even open
to the public) to see if you're subscribed to them, before responding to
a message addressed such as this?
As subscribers and submitters to such lists, we just have to learn to
deal with this reality. For example, I receive an average of a 100
messages per hour on this email address, -after- my employers spam
filters have knocked off over 90% of the incoming.
May I recommend you become an expert in procmail? That or speed
reading (and speed ignoring ;).
In a separate reply to this message, Alan Stern wrote:
> Everyone has his own taste.
This is not a matter of taste on these big lists. There is no other
practical alternative. Most of the burden of ultimate filtering must
be shifted to the recipients, and the senders asked only that they
err on the side of including every individual list or person already
on the address lists.
Joseph Fannin also replied:
> another free mail service which isn't so broken,
I'd recommend fastmail.fm as one of the least broken, most tech savvy
mail services. I believe that their free side includes IMAP, though
not POP support.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-02-17 7:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 21:45 USB regression (and other failures) in 2.6.2[45]* Andrew Buehler
2008-02-16 14:32 ` Oliver Pinter
2008-02-16 15:20 ` Alan Stern
2008-02-16 16:46 ` Andrew Buehler
2008-02-16 17:16 ` Alan Stern
2008-02-16 21:33 ` Andrew Buehler
2008-02-16 23:11 ` Alan Stern
2008-02-17 1:12 ` Andrew Buehler
2008-02-17 3:35 ` Alan Stern
2008-02-17 16:21 ` Andrew Buehler
2008-02-19 20:35 ` USB regression (and other failures) in 2.6.2[45]* - mostly resolved Andrew Buehler
2008-02-20 15:50 ` Alan Stern
2008-02-20 17:06 ` Andrew Buehler
2008-02-20 17:15 ` Alan Stern
2008-02-20 18:27 ` Andrew Buehler
2008-02-20 19:29 ` Alan Stern
2008-02-21 16:05 ` Andrew Buehler
2008-02-21 16:36 ` Alan Stern
2008-02-21 17:17 ` Greg KH
2008-02-21 19:43 ` Andrew Buehler
2008-02-21 20:02 ` Alan Stern
2008-02-17 4:10 ` [OT] GMail (was USB regression (and other failures)...) Joseph Fannin
2008-02-17 10:55 ` USB regression (and other failures) in 2.6.2[45]* Sergey Vlasov
2008-02-17 7:20 ` Paul Jackson [this message]
2008-02-17 16:17 ` Andrew Buehler
2008-02-17 16:20 ` Paul Jackson
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=20080217012006.3757dfae.pj@sgi.com \
--to=pj@sgi.com \
--cc=abuehler.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=jfannin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=stern@rowland.harvard.edu \
/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