From: Sam Ravnborg <sam@ravnborg.org>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Thunder from the hill <thunder@ngforever.de>,
Ion Badulescu <ionut@cs.columbia.edu>,
linux-kernel@vger.kernel.org
Subject: Re: KBuild 2.5 Impressions
Date: Sun, 2 Jun 2002 16:56:43 +0200 [thread overview]
Message-ID: <20020602165643.A1940@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0206012349360.671-100000@age.cs.columbia.edu> <Pine.LNX.4.44.0206020139510.29405-100000@hawkeye.luckynet.adm> <20020602160357.A1726@mars.ravnborg.org> <E17EWV7-0000Pv-00@starship>
On Sun, Jun 02, 2002 at 04:38:33PM +0200, Daniel Phillips wrote:
> You mean, fixing the bugs you introduced by trying to add it piecemeal?
> How about breaking it up where it makes sense to do so, and not breaking
> it up where it's silly.
Can we agree that it makes sense to add features one-by-one when
they are independent?
If thats the case then it is a simple matter of looking through the
features already present in kbuild-2.5.
Then to compare those features with the work done by Kai.
If the feature is worth it and can be introduced without the core,
then introduce it in kbuild-2.4.
This will make this specific feature visible to many people, and
those who feel against it can speak up.
> If you have a specific suggestion about which part should be broken out,
> feel free to provide details.
I already gave a list of features that could be broken out. Do you request
more information than that?
I already submitted 4 patches digged out from kbuild-2.5, one of them
introducing a bug. The bug was present in kbuild-2.5!
This bug was easy to spot since the patch was selfcontained, but
within several thousands of kbuild-2.5 source lines it would have been missed
most probarly.
Sam
next prev parent reply other threads:[~2002-06-02 14:54 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
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 [this message]
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=20020602165643.A1940@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ionut@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=thunder@ngforever.de \
/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