From: Paul P Komkoff Jr <i@stingr.net>
To: linux-kernel@vger.kernel.org
Subject: Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3
Date: Sat, 18 May 2002 17:15:36 +0400 [thread overview]
Message-ID: <20020518131536.GL21357@stingr.net> (raw)
In-Reply-To: <86256BBC.006D500D.00@smtpnotes.altec.com>
Replying to Wayne.Brown@altec.com:
> Personally, I wish that the only changes anybody made were to the kernel itself
> (new drivers added, existing performance improved, etc.) and that all the
> supporting tools and utilities just could be left alone. I know that's not
> going to happen, but anything that slows down changes in those extraneous things
> is fine with me. I'd be perfectly happy if *years* from now I was compiling
> Linux 45.10.12 with the same kbuild, CML, gcc and everything else that I'm using
> right now.
It seems like you stuck with existing toys forever, which can somewhat
indicate that your learning factor is extremely low
History knows many applications of such behavior. In short, it stops
improvements and breaks progress. And in a few words more, you can now
compile linux 2.2.(something) with egcs (something), and you will be able to
live in underground cave with stoneage tools *years* from now too.
--
Paul P 'Stingray' Komkoff 'Greatest' Jr // (icq)23200764 // (irc)Spacebar
PPKJ1-RIPE // (smtp)i@stingr.net // (http)stingr.net // (pgp)0xA4B4ECA4
next prev parent reply other threads:[~2002-05-18 13:15 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 19:51 kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3 Wayne.Brown
2002-05-17 20:09 ` Dave Jones
2002-05-17 20:25 ` Diego Calleja
2002-05-18 13:15 ` Paul P Komkoff Jr [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-19 10:26 Mike Galbraith
2002-05-18 10:25 Mike Galbraith
2002-05-18 17:32 ` Wayne.Brown
2002-05-18 18:11 ` Tomas Szepe
2002-05-18 21:15 ` DervishD
2002-05-20 4:31 ` Mike Fedyk
2002-05-20 5:09 ` Albert D. Cahalan
2002-05-20 5:18 ` Keith Owens
2002-05-20 14:29 ` Juan Quintela
2002-05-20 5:11 ` Keith Owens
2002-05-18 6:05 Wayne.Brown
2002-05-18 16:50 ` John Weber
2002-05-18 5:09 Wayne.Brown
2002-05-18 5:23 ` David Lang
2002-05-18 13:11 ` Diego Calleja
2002-05-17 22:59 Wayne.Brown
2002-05-17 23:14 ` Robert Love
2002-05-18 4:01 ` Horst von Brand
2002-05-18 12:57 ` Diego Calleja
2002-05-17 20:53 Wayne.Brown
2002-05-17 21:14 ` Andrew Morton
2002-05-17 21:42 ` William Lee Irwin III
2002-05-17 22:16 ` Kai Germaschewski
2002-05-17 22:34 ` William Lee Irwin III
2002-05-17 22:40 ` Larry McVoy
2002-05-18 0:41 ` Oliver Xymoron
2002-05-17 22:09 ` Nicolas Pitre
2002-05-18 0:38 ` Oliver Xymoron
2002-05-17 14:56 James Bottomley
2002-05-17 14:21 Wayne.Brown
2002-05-17 17:37 ` Adam Kropelin
2002-05-17 18:00 ` Robert Love
2002-05-16 22:42 Keith Owens
2002-05-17 0:10 ` Nicolas Pitre
2002-05-17 3:30 ` Tomas Szepe
2002-05-17 7:55 ` Russell King
2002-05-17 8:42 ` Miles Lane
2002-05-17 13:11 ` Dave Jones
2002-05-17 13:09 ` Denis Vlasenko
2002-05-17 8:17 ` Tomas Szepe
2002-05-17 13:39 ` Denis Vlasenko
2002-05-17 1:50 ` jeff millar
2002-05-17 2:04 ` Keith Owens
2002-05-17 2:26 ` Dave Jones
2002-05-17 7:11 ` Kenneth Johansson
2002-05-17 15:13 ` Nicolas Pitre
2002-05-17 15:19 ` Tomas Szepe
2002-05-17 15:42 ` Nicolas Pitre
2002-05-18 1:39 ` Keith Owens
2002-05-18 2:11 ` Nicolas Pitre
2002-05-18 2:19 ` Keith Owens
2002-05-17 18:19 ` Diego Calleja
2002-05-19 15:46 ` Pavel Machek
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=20020518131536.GL21357@stingr.net \
--to=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