From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: bugs in kernel 2.6.21 (both two release candidates) and kernel
Date: Tue, 6 Mar 2007 23:11:13 +0300 [thread overview]
Message-ID: <200703062311.13408.a1426z@gawab.com> (raw)
Linus Torvalds wrote:
> Finding somebody who is both technically top-notch *and* can work with
> people is so rare as to be something you shouldn't even look for. That's
> especially true since quite often, maintainership doesn't even come with a
> lot of glory - just a lot of work, and the expectation that you always be
> there.
There is a threaded approach; it's called XP, as in eXtremeProgramming.
It's a 2-person programming adventure, where each person covers the
shortcomings of the other. Doesn't work so well for bigEgos, though.
Thanks!
--
Al
reply other threads:[~2007-03-06 20:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200703062311.13408.a1426z@gawab.com \
--to=a1426z@gawab.com \
--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
all inboxes | Powered by JetHome®