From: Erik Mouw <erik@harddisk-recovery.com>
To: Jes Sorensen <jes@sgi.com>
Cc: Jeff Garzik <jeff@garzik.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Netdev List <netdev@vger.kernel.org>
Subject: Re: Private driver support emails should be avoided.
Date: Fri, 4 Aug 2006 17:41:47 +0200 [thread overview]
Message-ID: <20060804154146.GM31998@harddisk-recovery.com> (raw)
In-Reply-To: <yq0hd0sv9sk.fsf@jaguar.mkp.net>
On Fri, Aug 04, 2006 at 10:46:03AM -0400, Jes Sorensen wrote:
> >>>>> "Jeff" == Jeff Garzik <jeff@garzik.org> writes:
>
> Jeff> Just a reminder to folks out there... Don't send private driver
> Jeff> support emails.
>
> Jeff> I receive a lot of email. A lot. Not as much as Linus or
> Jeff> Andrew probably, but still sizable. And quite regularly, I will
> Jeff> receive a private email asking for help on a SATA or net driver
> Jeff> problem. The poster will include various details on their
> Jeff> problem, and ask for help debugging the problem. While the
> Jeff> email will indeed be skimmed -- looking at a mass of bug
> Jeff> reports, one can better detect patterns -- the people seeking
> Jeff> support privately will almost NEVER RECEIVE A RESPONSE.
>
> Very sane - I get some of it too, though less so these days :)
>
> What about writing this up and sticking it under
> Documentation/Reporting-Bugs or something so there's an easy reference
> to it?
The question came up on the linux-arm-kernel list as well. In
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2006-August/035259.html
Daniel Jacobowitz came up with this URL which could be uses as a
starting point:
http://www.eyrie.org/~eagle/faqs/questions.html
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
prev parent reply other threads:[~2006-08-04 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 22:05 Private driver support emails should be avoided Jeff Garzik
2006-08-04 14:46 ` Jes Sorensen
2006-08-04 15:41 ` Erik Mouw [this message]
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=20060804154146.GM31998@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=jeff@garzik.org \
--cc=jes@sgi.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).