From: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
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 17:51:12 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0209221744150.11808-100000@chaos.physics.uiowa.edu> (raw)
In-Reply-To: <3D8E4720.2050700@mandrakesoft.com>
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.
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.
I intentionally only printed a message and errored out in this case, and I
think that's more useful, particularly for people doing
make all 2>&1 > make.log
which now may take forever waiting for input.
--Kai
next prev parent reply other threads:[~2002-09-22 22:46 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 [this message]
2002-09-22 22:53 ` Jeff Garzik
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=Pine.LNX.4.44.0209221744150.11808-100000@chaos.physics.uiowa.edu \
--to=kai@tp1.ruhr-uni-bochum.de \
--cc=jgarzik@mandrakesoft.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).