From: Oliver Xymoron <oxymoron@waste.org>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Cc: netdev@oss.sgi.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pci-skeleton duplex check
Date: Fri, 13 Dec 2002 19:43:46 -0600 [thread overview]
Message-ID: <20021214014346.GA6029@waste.org> (raw)
In-Reply-To: <200212140019.gBE0JmDs006744@sandelman.ottawa.on.ca>
On Fri, Dec 13, 2002 at 07:19:47PM -0500, Michael Richardson wrote:
>
>
> >>>>> "Donald" == Donald Becker <becker@scyld.com> writes:
> Donald> The drivers in the kernel are now heavily modified and have significantly
> Donald> diverged from my version. Sure, you are fine with having someone else
> Donald> do the difficult and unrewarding debugging and maintainence work, while
> Donald> you work on just the latest cool hardware, change the interfaces and are
> Donald> concerned only with the current kernel version.
>
> I agree strongly with Donald.
>
> Interfaces should NEVER change in patch level versions.
> Just *DO NOT DO IT*.
>
> Go wild in odd-numbered.. get the interfaces right there.
> But leave them alone afterward.
Umm, if I recall correctly, they're rehashing a flame war about stuff
that occurred in 2.3. It doesn't need any additional kindling.
--
"Love the dolphins," she advised him. "Write by W.A.S.T.E.."
prev parent reply other threads:[~2002-12-14 1:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0212120857570.10674-100000@beohost.scyld.com>
2002-12-12 20:32 ` pci-skeleton duplex check Jeff Garzik
2002-12-12 21:11 ` Donald Becker
2002-12-12 21:39 ` Jeff Garzik
2002-12-13 1:18 ` Donald Becker
2002-12-13 9:17 ` David S. Miller
2002-12-13 16:56 ` Donald Becker
2002-12-13 18:29 ` David S. Miller
2002-12-14 13:17 ` Henning P. Schmiedehausen
2002-12-13 20:57 ` Jeff Garzik
2002-12-12 23:08 ` Ben Greear
2002-12-14 0:19 ` Michael Richardson
2002-12-14 1:43 ` Oliver Xymoron [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=20021214014346.GA6029@waste.org \
--to=oxymoron@waste.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=netdev@oss.sgi.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