From: "Martin.Knoblauch" <Martin.Knoblauch@teraport.de>
To: linux-kernel@vger.kernel.org
Cc: jalvo@mbay.net, kai@tp1.ruhr-uni-bochum.de
Subject: Re: If you want kbuild 2.5, tell Linus
Date: Tue, 4 Jun 2002 09:04:00 +0200 [thread overview]
Message-ID: <200206040903.33625.Martin.Knoblauch@teraport.de> (raw)
>>
>>"KEITH, I'LL MERGE KBUILD 2.5"
>>
>>
>>but he must have some reason. Perhaps I don't understand it because I
>>haven't to make happy to such mass of people ;)
>
>
>Linus is doing things in his style. He has chosen a trusted lieutenant
>(Kai) who is not a committed "true believer". Kai will work through
>kbuild 2.5 and feed it to Linus in small batches. Keith will (should)
>work with Kai. Thus a delegation and filtering step so Linus doesn't
>have to understand every aspect of the change. Kai has done it before
>(ISDN code) and Linus trusts him.
>
>
>Management 101...
Basically correct with two "but"s. It seems that Linus has only very
recently stated that Kai should do the work. And apparently he did not
tell Keith very clearly how to to proceed. Also, from the qouted link:
http://marc.theaimsgroup.com/?l=linux-kernel&m=102304528224527&w=2
it is not clear to me whether this will lead to kbuild-2.5 "(or whatever
subset of them you find appropriate)". So I have some sympathy for Keith
for being impatient and worried about "his" project. Maybe things would
calm down if Kai could state his intentions and timetable?
While delegation of authorithy is of course Managment 101, lack of clear
communication is probably in the same book - high on the "NONO" and
"popular reasons for failure" lists. (Have some experience on that. From
both sides :-(
And the whole community is still eagerly waiting for the timetable (as
someone else already pointed out). I don't really care how it is done, as
long as it is done at all and we get the 2.5 benefits before 2010 (no,
that was for IDE :-).
Martin
--
------------------------------------------------------------------
Martin Knoblauch | email: Martin.Knoblauch@TeraPort.de
TeraPort GmbH | Phone: +49-89-510857-309
C+ITS | Fax: +49-89-510857-111
http://www.teraport.de | Mobile: +49-170-4904759
next reply other threads:[~2002-06-04 7:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 7:04 Martin.Knoblauch [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 21:01 Jesse Pollard
2002-06-06 21:36 ` Tomas Szepe
2002-06-10 21:43 ` Bill Davidsen
2002-06-07 1:39 ` Mark Mielke
2002-06-07 15:31 ` Thunder from the hill
2002-06-08 15:51 ` David Woodhouse
2002-06-08 15:54 ` Thunder from the hill
2002-06-03 17:33 Martin.Knoblauch
2002-06-03 17:48 ` Thunder from the hill
2002-06-03 15:29 Wayne.Brown
2002-06-03 16:05 ` Mark Mielke
2002-06-03 17:24 ` Thunder from the hill
2002-06-03 13:58 Keith Owens
2002-06-03 13:20 ` Martin Dalecki
2002-06-03 14:36 ` Tomas Szepe
2002-06-03 14:15 ` Daniel Phillips
2002-06-03 17:51 ` Austin Gonyou
2002-06-03 22:10 ` Diego Calleja
2002-06-03 22:24 ` John Alvord
2002-06-03 22:34 ` Thunder from the hill
2002-06-03 23:10 ` Diego Calleja
2002-06-04 1:26 ` Daniel Phillips
2002-06-06 19:31 ` Kai Henningsen
2002-06-06 20:56 ` Tom Rini
2002-06-07 0:30 ` Daniel Phillips
2002-06-07 15:29 ` Thunder from the hill
2002-06-03 14:33 ` Nicolas Pitre
2002-06-03 15:27 ` Peter Wächtler
2002-06-03 16:09 ` Nicolas Pitre
2002-06-03 14:54 ` Daniel Phillips
2002-06-03 17:26 ` Olivier Galibert
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=200206040903.33625.Martin.Knoblauch@teraport.de \
--to=martin.knoblauch@teraport.de \
--cc=jalvo@mbay.net \
--cc=kai@tp1.ruhr-uni-bochum.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
all inboxes | Powered by JetHome®