From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: pci-skeleton duplex check
Date: Sat, 14 Dec 2002 13:17:20 +0000 (UTC) [thread overview]
Message-ID: <atfb10$nc6$1@forge.intermeta.de> (raw)
In-Reply-To: 20021213.102918.102902274.davem@redhat.com
"David S. Miller" <davem@redhat.com> writes:
> From: Donald Becker <becker@scyld.com>
> Date: Fri, 13 Dec 2002 11:56:17 -0500 (EST)
>
> The development criteria used to be technically based, and that is still
> the public statement. Now, as your statement makes clear, working code
> is an irrelevant criteria.
>No, working code is only part of the equation. If you're a total and
>complete asshole, your work is likely to get lost to the sands of
>time. In such a case nobody wants to deal with you.
The IDE code and one of its current maintainers disproves your point.
I did notice that it was you and not Donald who started using swear
words. Ego problem?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2002-12-14 13:09 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 [this message]
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
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='atfb10$nc6$1@forge.intermeta.de' \
--to=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