From: Daniel Phillips <phillips@bonn-fries.net>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: Keith Owens <kaos@ocs.com.au>,
Linus Torvalds <torvalds@transmeta.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: KBuild 2.5 Impressions
Date: Sun, 2 Jun 2002 08:51:21 +0200 [thread overview]
Message-ID: <E17EPCz-0000Jr-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44.0206012349360.671-100000@age.cs.columbia.edu>
On Sunday 02 June 2002 06:03, you wrote:
> On Fri, 31 May 2002, Daniel Phillips wrote:
> What you and other very vocal proponents of kbuild25 don't understand is
> that you need break it up __functionally__. That is, add one feature at a
> time. That way, good features can be added without much of a discussion,
> and debatable features can be, well, debated.
>
> Unfortunately, I don't see Keith doing this anytime soon. He's too much in
> love with his baby to risk seeing parts of it being thrown away, so he's
> taking an all-or-nothing attitude.
Fortunately, he's got help now:
http://marc.theaimsgroup.com/?a=102296100300003&r=1&w=2
> Fortunately, it is precisely what Kai is doing. He deserves a big THANKS
> for doing it, not your silly bashing. I also saw some good work on this
> from Sam Ravnborg on the list.
If I got the impression that Kai was actually trying to work with the team,
I'd thank him for that. He appears to be doing just the opposite, and I
stand by my comment that that is divisive. He could accomplish the same
thing result he wants - patching up old kbuild - and bring parts of kbuild
2.5 into the tree, reducing the size of that patch *at the same time*,
instead of (apparently) trying to marginalize that work. That is what I'd
call cooperation.
We have a perfect - and rare - situation here where the two can coexist in
the same tree, and may the best and fastest eventually predominate. Let's
take advantage of that: let's have both in parallel for a while.
--
Daniel
next prev parent reply other threads:[~2002-06-02 6:52 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 9:45 KBuild 2.5 Impressions Daniel Phillips
2002-05-30 12:50 ` Martin Dalecki
2002-05-30 14:08 ` Kenneth Johansson
2002-05-30 13:28 ` Paul P Komkoff Jr
2002-05-30 21:55 ` Ion Badulescu
2002-05-30 22:29 ` Thunder from the hill
2002-05-30 23:19 ` Daniel Phillips
2002-05-31 0:09 ` David Lang
2002-05-31 0:29 ` Daniel Phillips
2002-05-31 0:32 ` Larry McVoy
2002-06-03 7:21 ` Rusty Russell
2002-05-31 0:13 ` Kenneth Johansson
2002-05-31 0:47 ` Daniel Phillips
2002-05-31 1:20 ` Skip Ford
2002-05-31 1:24 ` Daniel Phillips
2002-05-31 13:48 ` Tomas Szepe
2002-05-31 14:28 ` Nicolas Pitre
2002-05-31 15:21 ` Thunder from the hill
[not found] ` <Pine.LNX.4.44.0205302129120.29405-100000@hawkeye.luckynet.adm>
2002-05-31 4:01 ` Skip Ford
2002-05-31 4:46 ` KBuild 2.5 Migration Daniel Phillips
2002-05-31 5:12 ` Skip Ford
2002-05-31 0:48 ` KBuild 2.5 Impressions Nicolas Pitre
2002-05-31 3:29 ` Hua Zhong
2002-05-31 3:39 ` Daniel Phillips
2002-05-31 3:55 ` Thunder from the hill
2002-06-02 4:03 ` Ion Badulescu
2002-06-02 6:51 ` Daniel Phillips [this message]
2002-06-02 7:58 ` Thunder from the hill
2002-06-02 14:03 ` Sam Ravnborg
2002-06-02 14:38 ` Daniel Phillips
2002-06-02 14:56 ` Sam Ravnborg
2002-06-02 15:05 ` Thunder from the hill
2002-06-02 15:16 ` Daniel Phillips
2002-06-02 18:26 ` Sam Ravnborg
2002-06-02 18:39 ` Thunder from the hill
2002-06-02 18:57 ` Ion Badulescu
2002-06-02 19:15 ` Thunder from the hill
2002-06-03 2:04 ` Kai Germaschewski
2002-06-02 15:47 ` Thunder from the hill
2002-06-02 11:21 ` Peter Osterlund
2002-06-02 11:37 ` Thunder from the hill
2002-06-02 11:53 ` Peter Osterlund
2002-06-02 12:03 ` Thunder from the hill
2002-06-02 12:09 ` Thunder from the hill
2002-06-02 12:51 ` Peter Osterlund
2002-06-02 14:00 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 2:49 Dan Kegel
2002-06-03 3:28 ` Linus Torvalds
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=E17EPCz-0000Jr-00@starship \
--to=phillips@bonn-fries.net \
--cc=ionut@cs.columbia.edu \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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