From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: kbuild (was Re: Versioning of tree)
Date: Thu, 21 Oct 2004 19:03:16 -0400 [thread overview]
Message-ID: <41784034.9050107@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410211005320.2171@ppc970.osdl.org>
Linus Torvalds wrote:
> We already have the concept of "localversion*" files that get appended to
> the build.[...]
Just to tangent a bit... I've been meaning to throw out a public kudos
to Sam, Kai, Roman and the other kbuild/kconfig hackers. The 2.6 kbuild
and kconfig system is a _huge_ improvement over 2.4.x.
These days I use
echo "-sataN" > localversion
heavily, and it's been quite helpful. The separation of src/obj
directories, the default verbosity level, 'make allyesconfig', and the
elimination of recursive Makefile invocations are just some of the
things that stick out as positive improvements that impact me on a daily
basis.
Thanks guys!
Jeff
next prev parent reply other threads:[~2004-10-21 23:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 6:49 Versioning of tree Benjamin Herrenschmidt
2004-10-20 7:22 ` Len Brown
2004-10-20 14:33 ` Linus Torvalds
2004-10-21 1:38 ` Benjamin Herrenschmidt
2004-10-21 15:33 ` Måns Rullgård
2004-10-21 15:48 ` Linus Torvalds
2004-10-21 16:49 ` Jeff Garzik
2004-10-21 17:10 ` Linus Torvalds
2004-10-21 23:03 ` Jeff Garzik [this message]
2004-10-30 23:34 ` kbuild (was Re: Versioning of tree) Sam Ravnborg
2004-10-25 23:47 ` Versioning of tree Ryan Anderson
2004-10-26 11:49 ` David Vrabel
2004-10-26 12:26 ` Ryan Anderson
2004-10-26 12:58 ` David Vrabel
2004-10-26 19:08 ` Sam Ravnborg
2004-10-26 18:04 ` Ryan Anderson
2004-10-26 19:11 ` Ian Campbell
2004-10-27 8:38 ` Ryan Anderson
2004-10-27 11:37 ` Sam Ravnborg
2004-10-20 8:22 ` Jeff Garzik
2004-10-20 8:39 ` Benjamin Herrenschmidt
2004-10-20 10:36 ` Måns Rullgård
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=41784034.9050107@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.