From: Tomas Szepe <szepe@pinerecords.com>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel configurator request
Date: Mon, 6 Jan 2003 18:54:43 +0100 [thread overview]
Message-ID: <20030106175443.GP5984@louise.pinerecords.com> (raw)
In-Reply-To: <200301061725.h06HP8Ur000947@darkstar.example.net>
> [john@grabjohn.com]
>
> Obviously I can work around this, but it would seem to me to be better
> to have the kernel configurators generate .config files like this:
>
> #
> # Automatically generated make config: don't edit
> #
>
> #
> # Very general options
> #
> [Very general options]
[snip]
John,
AFAIK all you have to do to make this reality is add a "comment" clause
where you need it.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-01-06 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 17:25 Kernel configurator request John Bradford
2003-01-06 17:54 ` Tomas Szepe [this message]
2003-01-09 18:41 ` John Bradford
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=20030106175443.GP5984@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=john@grabjohn.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox