From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Paul P Komkoff Jr <i@stingr.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.19 - What's up with the kernel build?
Date: Wed, 29 May 2002 16:58:32 -0400 [thread overview]
Message-ID: <3CF540F8.6000802@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205291519270.9971-100000@chaos.physics.uiowa.edu> <20020529205005.GN422@stingr.net>
Paul P Komkoff Jr wrote:
>Replying to Kai Germaschewski:
>
>
>>There is still quite a bit left to do (in particular improving
>>dependency generation and modversions handling), but I think it makes
>>sense to explain what happened so far.
>>
>>There's also some points (marked with >>>) where I'd like to get
>>feedback on how things should be handled in the future.
>>
>>
>
>May I ask you just one questin?
>Have you read (yet) kbuild25 ?
>
>Ahh, no, another one.
>Is this a "signs" of kbuild25 being thrown away like cml2 ?
>If yes, then I am very unhappy person now (c) ac
>
>Played with kbuild25 today I migrated 2.4.19-pre8-ac5-s2 to it. Now make -f
>Makefile-2.5 is a preferred way to make here. New system is much cleaner,
>and don't need that mess of makedep and listmultis. But hey, people you
>should already know that whilst you trying to install a couple of new nails
>to rotten construct to help it stay for another couple of time intervals ...
>
>
Well, I really like Keith's kbuild25 too, but Linus said (at least once)
he wanted an evolution to a new build system... not an unreasonable
request to at least consider. Despite Keith's quality of code (again --
I like kbuild25), his 3 patch submissions seemed a lot like ultimatums,
very "take it or leave it dammit". Not the best way to win friends and
influence people.
If Keith is indeed leaving it, I'm hoping someone will maintain it, or
work with Kai to integrate it into 2.5.x.
Jeff
next prev parent reply other threads:[~2002-05-29 21:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 20:22 2.5.19 - What's up with the kernel build? Kai Germaschewski
2002-05-29 20:50 ` Paul P Komkoff Jr
2002-05-29 20:58 ` Jeff Garzik [this message]
2002-05-29 22:38 ` Nicolas Pitre
2002-05-29 22:56 ` Thunder from the hill
2002-05-29 23:18 ` Nicolas Pitre
2002-05-29 23:29 ` Daniel Phillips
2002-05-29 23:06 ` Tomas Szepe
2002-05-29 23:40 ` Daniel Phillips
2002-05-30 0:17 ` Nicolas Pitre
2002-05-30 0:36 ` Daniel Phillips
2002-05-30 0:42 ` Jeff Garzik
2002-05-30 0:47 ` Robert Love
2002-06-03 6:49 ` Rusty Russell
2002-05-30 2:23 ` Nicolas Pitre
2002-05-30 2:30 ` Daniel Phillips
2002-05-30 2:00 ` Kai Germaschewski
2002-05-30 2:17 ` Daniel Phillips
2002-05-30 8:45 ` Jeff Garzik
2002-05-30 8:54 ` Erik Andersen
2002-05-30 9:01 ` Russell King
2002-05-30 9:32 ` Erik Andersen
2002-05-30 13:22 ` Kai Germaschewski
2002-05-29 22:14 ` Martin Dalecki
2002-05-29 23:22 ` Tom Rini
2002-05-29 22:45 ` Martin Dalecki
2002-05-30 0:33 ` Kai Germaschewski
2002-06-01 3:01 ` Kernel compile quiet mode Kevin O'Connor
2002-06-01 7:34 ` Kai Germaschewski
2002-06-01 15:08 ` Kevin O'Connor
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=3CF540F8.6000802@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=i@stingr.net \
--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