From: Brendan J Simon <brendan.simon@bigpond.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: [kbuild-devel] Re: linux kernel conf 0.8
Date: Thu, 10 Oct 2002 00:14:10 +1000 [thread overview]
Message-ID: <3DA439B2.3000801@bigpond.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210091546070.8911-100000@serv
Roman Zippel wrote:
>>Well, my basic preference is
>>
>>* something other than Config.new (the original name in your config system)
>>* something other than Config.in
>>
>>I think it is a mistake to name a totally different format the same name
>>as an older format... even "config.in" would be better than "Config.in"...
>>
>>
>
>My first plan was to use Config.in, but I can't overwrite the old files
>yet, so I named it Config.new. Personally I only prefer that it starts
>with a capital letter (like Makefile, Readme), so it's at the top of a
>dir listing, but otherwise I don't care much about the name.
>
Simple and boring but how about "Config2.in" or "Config-2.in" ???
Regards,
Brendan Simon.
next prev parent reply other threads:[~2002-10-09 14:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0210081830350.4396-100000@home.transmeta.com>
2002-10-09 12:01 ` linux kernel conf 0.8 Roman Zippel
2002-10-09 13:35 ` Jeff Garzik
2002-10-09 13:55 ` Roman Zippel
2002-10-09 14:07 ` Jeff Garzik
2002-10-09 14:14 ` Brendan J Simon [this message]
2002-10-09 14:28 ` [kbuild-devel] " Jeff Garzik
2002-10-09 14:24 ` Brendan J Simon
2002-10-09 14:34 ` Randy.Dunlap
2002-10-09 14:45 ` J.A. Magallon
2002-10-09 15:14 ` Roman Zippel
2002-10-09 15:16 ` Linus Torvalds
2002-10-09 15:19 ` Randy.Dunlap
2002-10-09 16:29 ` Roman Zippel
2002-10-09 16:40 ` Christoph Hellwig
2002-10-09 18:39 ` Roman Zippel
2002-10-09 18:52 ` Peter Samuelson
2002-10-09 19:28 ` Randy.Dunlap
2002-10-09 19:39 ` Sam Ravnborg
2002-10-09 19:47 ` Randy.Dunlap
2002-10-09 14:55 ` [kbuild-devel] " Roman Zippel
2002-10-09 17:16 ` Sam Ravnborg
2002-10-09 17:37 ` Linus Torvalds
2002-10-09 17:55 ` Sam Ravnborg
2002-10-09 18:47 ` Linus Torvalds
2002-10-09 19:26 ` Sam Ravnborg
2002-10-09 20:41 ` Jeff Garzik
2002-10-09 22:49 ` Roman Zippel
2002-10-10 14:18 ` Jeff Garzik
2002-10-10 17:29 ` Sam Ravnborg
2002-10-10 17:32 ` Jeff Garzik
2002-10-10 17:51 ` Sam Ravnborg
2002-10-09 23:49 ` [kbuild-devel] " Brendan J Simon
2002-10-09 18:35 ` Jeff Garzik
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=3DA439B2.3000801@bigpond.com \
--to=brendan.simon@bigpond.com \
--cc=jgarzik@pobox.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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