From: Andrew Morton <akpm@digeo.com>
To: "Joseph D. Wagner" <wagnerjd@prodigy.net>
Cc: "'Matt Domsch'" <Matt_Domsch@Dell.com>,
"'Linux Kernel Development List'" <linux-kernel@vger.kernel.org>
Subject: Re: [CFT][PATCH 2.5] x86 BIOS Enhanced Disk Drive services
Date: Sat, 12 Oct 2002 22:29:22 -0700 [thread overview]
Message-ID: <3DA904B2.CC4E6738@digeo.com> (raw)
In-Reply-To: 001d01c27274$42da70e0$b7261c43@joe
"Joseph D. Wagner" wrote:
>
> Sure! Will I get paid? Cause I sure as hell am not working for free.
>
External testing by the long-suffering body of well-meaning users
is a critical factor in kernel development.
I see no reason why a prospective contribution from a Dell employee
should be denied that.
As someone once said: "In case you've forgotten, this is the Linux
Kernel Development List, for DEVELOPERS. Take your cyber-political,
cyber-theology, and cyber-philosophy elsewhere!"
Oh. That was you.
prev parent reply other threads:[~2002-10-13 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20BF5713E14D5B48AA289F72BD372D68BC0284@AUSXMPC122.aus.amer.dell.com>
2002-10-10 3:31 ` [PATCH] x86 BIOS Enhanced Disk Drive services Matt Domsch
2002-10-13 3:55 ` [CFT][PATCH 2.5] " Matt Domsch
2002-10-13 4:51 ` Joseph D. Wagner
2002-10-13 5:29 ` Andrew Morton [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=3DA904B2.CC4E6738@digeo.com \
--to=akpm@digeo.com \
--cc=Matt_Domsch@Dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wagnerjd@prodigy.net \
/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