From: Nicolas Schier <nsc@kernel.org>
To: Franco Martelli <martellif67@gmail.com>
Cc: nathan@kernel.org, rdunlap@infradead.org, corbet@lwn.net,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/1] Kconfig: Added compare capabilities for mconf
Date: Tue, 11 Nov 2025 15:48:35 +0100 [thread overview]
Message-ID: <aRNMww8YU_7dKwK3@derry.ads.avm.de> (raw)
In-Reply-To: <20251030141342.159994-2-martellif67@gmail.com>
Hi Franco,
thanks for your contribution. Some notes below:
On Thu, Oct 30, 2025 at 03:13:42PM +0100, Franco Martelli wrote:
> This patch allows to compare the tristate value of two .config files
> inline, symbol by symbol, in mconf (make menuconfig) only. It can be
> really useful when customizing the .config file.
>
> When a new stable release of a distribution is available, in the Linux
> kernel many things has changed, this patch comes in help in this
> situations, it allows to easily compare the customized .config file
> built for the previous version of the distribution, with the one
> provided by the new software distribution, used as reference.
> Generally it can be helpful when the differences between .config files
> are huge, because you can navigate across them in the menu window.
>
> The patch has a limitation, it only show the tristate value (Y/N/M) not
> differences for symbol with a value (string), but it also marks with a
> "#" the symbol missing in the loaded .config, meaning therefore the
> symbol as a new feature.
I must confess, that I am not convinced yet, that this will be helpful
for general purposes. Yes, large changes in .config files are not easy
to parse, but I do not see how your solution is easier to handle than
the use of scripts/diffconfig, other than not showing removed config
options.
>
> o I've also added support for the more canonical <F1> key to show inline
> help window, in addition to <?> and <h> keys.
Please split-off logical these independent changes into separate
patches (Add support for 'F1' hot-key).
Using simple letters (here 'h') as hot-keys is not a good idea as those
are already used for jumping through the currently shown menu item
(cp. highlighted letters in menu config screens).
> o By pressing the <F2> or <D> key you will get a view with all the
> symbol differences listed.
>
> o By pressing the <F4> or <F> key you'll save to a file the differences.
While the list might be helpful for comparing two config files, a large
list within an ncurses window does not look like a good thing to me.
When I save the list to a file (F4), I'd rather choose the output of
diffconfig for evaluation -- as it is more complete and has a layout
that looks more straight-forward and clear to me.
> o Added help text that it describes the new features.
>
> This software is under GPL-2.0 license.
Please note that the whole Linux kernel source and its build system is
GPL-2.0 per se, cp. COPYING and the SPDX header line in each file.
>
> Changelog:
> ----------
>
> scripts/kconfig/confdata.c:
> ---------------------------
>
> Silenced a warning emitted when parsing the .config file to compare.
[...]
Please put any patch changelog below the triple-dash line ('---').
I have not looked at the code, yet, as I have doubts regarding the
usefulness (see above).
Iff nobody mentions strong interest in these changes, please re-evaluate
if it makes sense for you to invest into a v5.
Kind regards,
Nicolas
next prev parent reply other threads:[~2025-11-11 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 14:13 [PATCH 0/1] Kconfig: Added compare capabilities for mconf Franco Martelli
2025-10-30 14:13 ` [PATCH 1/1] " Franco Martelli
2025-11-11 14:48 ` Nicolas Schier [this message]
2025-11-11 20:37 ` Franco Martelli
-- strict thread matches above, loose matches on Subject: below --
2025-06-01 18:40 [PATCH 0/1] kconfig: comparison feature between two .config files added to mconf Franco Martelli
2025-06-01 18:40 ` [PATCH 1/1] Kconfig: Added compare capabilities for mconf Franco Martelli
2025-06-02 0:59 ` Randy Dunlap
2025-06-02 13:41 ` Franco Martelli
2025-06-02 13:52 ` Miguel Ojeda
2025-06-02 16:42 ` Randy Dunlap
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=aRNMww8YU_7dKwK3@derry.ads.avm.de \
--to=nsc@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=martellif67@gmail.com \
--cc=nathan@kernel.org \
--cc=rdunlap@infradead.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).