public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Nicolas Pitre <nico@cam.org>,
	Thunder from the hill <thunder@ngforever.de>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
	Paul P Komkoff Jr <i@stingr.net>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.19 - What's up with the kernel build?
Date: Thu, 30 May 2002 01:29:01 +0200	[thread overview]
Message-ID: <E17DCsH-0006py-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44.0205291909440.23147-100000@xanadu.home>

On Thursday 30 May 2002 01:18, Nicolas Pitre wrote:
> On Wed, 29 May 2002, Thunder from the hill wrote:
> > 
> > On Wed, 29 May 2002, Nicolas Pitre wrote:
> > > So it looks like someone else will have to volunteer to split kbuild25 into
> > > multiple small patches and feed them "piecemeal" to Linus before we ever see
> > > it into the kernel tree.
> > 
> > Well, I would, but... wasn't Kai on that already?
> 
> No.
> 
> Kai is only banging on the current build system to make it somewhat more
> palatable.  While this is certainly useful today, those efforts would
> probably produce a better system in the long run if they were directed at
> kbuild25 instead.
> 
> Or maybe people just don't care enough about the build system for kbuild25
> to be worth it...

Omigod, don't even think that.  Kbuild 2.5 is faster and better than the
current kbuild.  I, for one, am waiting - impatiently - for the thing to get
in the tree.  The current build system is slow and unreliable, and don't even
think of trying to build two different architectures in the same source tree
at the same time.

-- 
Daniel

  reply	other threads:[~2002-05-29 23:29 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
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 [this message]
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=E17DCsH-0006py-00@starship \
    --to=phillips@bonn-fries.net \
    --cc=i@stingr.net \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --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