All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Date: Sun, 07 Apr 2002 17:38:36 +0200	[thread overview]
Message-ID: <3CB067FC.12ECC11C@linux-m68k.org> (raw)
In-Reply-To: <28835.1018191216@ocs3.intra.ocs.com.au>

Hi,

Keith Owens wrote:

> It takes time to do all the analysis to work out what has changed and
> what has been affected.  You might know that you only changed one file
> but kernel build and make don't know that until they have checked
> everything.  Changing one file or specifying a command override might
> affect one file or it might affect the entire kernel.

Doing that analysis once is fine. After that it should know what it has
to check if I only want foo/bar.o recompiled and that shouldn't take
that long.

> Otherwise let kbuild work out what has been affected.

That's the problem with kernel hackers, they want to know what's going
on. :)

bye, Roman

  reply	other threads:[~2002-04-07 15:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 11:26 Announce: Kernel Build for 2.5, Release 2.0 is available Keith Owens
2002-04-06  2:03 ` Keith Owens
2002-04-06 16:35   ` Russell King
2002-04-06 23:12     ` Keith Owens
2002-04-06 18:17   ` Larry McVoy
2002-04-07 14:18 ` Roman Zippel
2002-04-07 14:28   ` Keith Owens
2002-04-07 14:51     ` Roman Zippel
2002-04-07 14:53       ` Keith Owens
2002-04-07 15:38         ` Roman Zippel [this message]
2002-04-07 23:35         ` [kbuild-devel] " Brendan J Simon
2002-04-08  8:50   ` Keith Owens
2002-04-08  9:06     ` Roman Zippel
2002-04-08 12:04 ` Keith Owens
2002-04-09 13:08   ` Keith Owens
2002-04-09 19:00     ` [kbuild-devel] " Thomas Duffy
2002-04-10  1:11       ` Keith Owens
2002-04-10 11:48     ` Keith Owens
2002-04-14 13:23     ` Keith Owens
2002-04-16  1:58       ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2002-04-06  7:20 Keith Owens
2002-04-07  0:51 ` Keith Owens
     [not found] <p73k7rms6ba.fsf@oldwotan.suse.de.suse.lists.linux.kernel>
     [not found] ` <7853.1018011163@ocs3.intra.ocs.com.au.suse.lists.linux.kernel>
2002-04-05 14:37   ` Andi Kleen
2002-04-05 14:52     ` Keith Owens
     [not found] <7022.1018005968@ocs3.intra.ocs.com.au.suse.lists.linux.kernel>
2002-04-05 12:01 ` Andi Kleen
2002-04-05 12:52   ` Keith Owens
2002-04-05 13:29     ` Russell King
2002-04-05 14:33       ` Keith Owens
2002-04-05 10:59 Keith Owens
2002-04-05 11:09 ` Pavel Machek
2002-04-05 11:23   ` Sebastian Heidl
2002-04-05 18:25     ` Mike Fedyk
2002-04-06 18:31       ` Peter Samuelson
2002-04-08 16:16   ` Matthias Andree

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=3CB067FC.12ECC11C@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=kaos@ocs.com.au \
    --cc=kbuild-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.