From: "David S. Miller" <davem@redhat.com>
To: becker@scyld.com
Cc: jgarzik@pobox.com, rl@hellgate.ch, netdev@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: pci-skeleton duplex check
Date: Fri, 13 Dec 2002 10:29:18 -0800 (PST) [thread overview]
Message-ID: <20021213.102918.102902274.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0212131109180.1399-100000@beohost.scyld.com>
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.
Welcome to the real world where you have to interact with other human
beings (not just be technically capable) in order to accomplish
things.
It's always been like this Donald. If you piss off, or are a jerk to,
the primary maintainers you're going to get the short end of the
stick.
next prev parent reply other threads:[~2002-12-13 18:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 13:24 pci-skeleton duplex check Roger Luethi
2002-12-12 2:42 ` Donald Becker
2002-12-12 13:20 ` Roger Luethi
2002-12-12 14:11 ` Donald Becker
2002-12-12 20:32 ` 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 [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=20021213.102918.102902274.davem@redhat.com \
--to=davem@redhat.com \
--cc=becker@scyld.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rl@hellgate.ch \
/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).