From: John Bradford <john@grabjohn.com>
To: linux-kernel@vger.kernel.org
Cc: szepe@pinerecords.com
Subject: Kernel configurator request
Date: Mon, 6 Jan 2003 17:25:08 +0000 (GMT) [thread overview]
Message-ID: <200301061725.h06HP8Ur000947@darkstar.example.net> (raw)
Traditionally, kernel configurators have produced .config files like
this:
#
# Automatically generated make config: don't edit
#
[Very general options]
#
# Code maturity level options
#
[Code maturity level options]
#
# General setup
#
[General setup options]
..etc...
My kernel bug database parses .config files, and currently, if it
detects comments, (which don't appear to be commented out options), it
uses them to present a sorted list of options to the user. (If there
are no comments, it remains uncategorised).
The problem is that at the moment the first, very general options, get
categorised under "Automatically generated make config: don't edit".
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]
#
# Code maturity level options
#
[Code maturity level options]
#
# General setup
#
[General setup options]
..etc...
John.
next reply other threads:[~2003-01-06 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 17:25 John Bradford [this message]
2003-01-06 17:54 ` Kernel configurator request Tomas Szepe
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=200301061725.h06HP8Ur000947@darkstar.example.net \
--to=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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