From: Robert Love <rml@tech9.net>
To: hps@intermeta.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Networking/Becker et al [was Re: pci-skeleton duplex check]
Date: 14 Dec 2002 15:47:21 -0500 [thread overview]
Message-ID: <1039898841.855.1684.camel@phantasy> (raw)
In-Reply-To: <atfblt$nh2$1@forge.intermeta.de>
On Sat, 2002-12-14 at 08:28, Henning P. Schmiedehausen wrote:
> e) put an alan-cox-like entity between him and the linux kernel developers
> which translates. Worked terrific for Andre Hedrick. :-)
Isn't that what Jeff is?
No one seems to have a problem working with him. Jeff is the
maintainer. An "Alan Cox" buffer works great when the maintainer is
loony but Jeff is the maintainer and not a wacko. He can work with
Donald just fine if Donald plays the game.
(And I shall add I hope he does, because Donald is a gifted hacker)
Robert Love
next prev parent reply other threads:[~2002-12-14 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 17:22 Networking/Becker et al [was Re: pci-skeleton duplex check] Larry McVoy
2002-12-13 21:19 ` Jeff Garzik
2002-12-14 13:28 ` Henning P. Schmiedehausen
2002-12-14 15:21 ` Rik van Riel
2002-12-14 20:47 ` Robert Love [this message]
2002-12-15 9:54 ` Henning P. Schmiedehausen
2002-12-15 12:32 ` Adrian Bunk
2002-12-15 13:06 ` Henning P. Schmiedehausen
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=1039898841.855.1684.camel@phantasy \
--to=rml@tech9.net \
--cc=hps@intermeta.de \
--cc=linux-kernel@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