From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Sam Ravnborg <sam@ravnborg.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [kbuild-devel] linux kernel conf 0.6
Date: Sun, 22 Sep 2002 18:53:58 -0400 [thread overview]
Message-ID: <3D8E4A06.5010603@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209221744150.11808-100000@chaos.physics.uiowa.edu
Kai Germaschewski wrote:
> On Sun, 22 Sep 2002, Jeff Garzik wrote:
>
>
>>One cosmetic thing I mentioned to Roman, Config.new needs to be changed
>>to something better, like conf.in or build.conf or somesuch.
>
>
> I agree. (But I'm not particularly good at coming up with names ;)
> build.conf is maybe not too bad considering that there may be a day where
> it is extended to support "<driver>.conf" as well.
We want to make sure the config format is extensible in case we want to
add Makefile rules or some other metadata (i.e. <driver>.conf contains
all config/make info needed to build a driver, just drop it in)
> One other thing I wanted to mention but forgot was that lkc now
> does a quiet "make oldconfig" when .config changed or does not exist,
> which is changed behavior.
Can you elaborate a bit on that? 'make oldconfig' is one of the things
we want to keep working as-is... That was a downside of ESR's system.
If you're saying "silent" as in, if-no-changes-occurred or
defconfig-copied-as-is, that's cool...
Jeff
next prev parent reply other threads:[~2002-09-22 22:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 23:16 linux kernel conf 0.6 Roman Zippel
2002-09-20 5:10 ` [kbuild-devel] " Sam Ravnborg
2002-09-22 15:24 ` Roman Zippel
2002-09-22 22:36 ` Kai Germaschewski
2002-09-22 22:41 ` Jeff Garzik
2002-09-22 22:51 ` Kai Germaschewski
2002-09-22 22:53 ` Jeff Garzik [this message]
2002-09-22 23:03 ` Kai Germaschewski
2002-09-23 1:48 ` Jeff Garzik
2002-09-22 23:07 ` Roman Zippel
2002-09-22 23:19 ` Kai Germaschewski
2002-09-22 23:30 ` Roman Zippel
2002-09-23 1:50 ` Jeff Garzik
2002-09-23 19:59 ` Sam Ravnborg
2002-10-03 11:17 ` Roman Zippel
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=3D8E4A06.5010603@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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.