From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Petr Vorel <pvorel@suse.cz>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Paul Bolle <pebolle@tiscali.nl>, Michal Marek <mmarek@suse.cz>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [PATCH v3 1/1] kconfig: menuconfig make "selected by:" readable
Date: Wed, 4 Oct 2017 18:18:39 +0900 [thread overview]
Message-ID: <CAK7LNASbFBSA=aQUkYVWBbSA9F7UHc2=GAoSFhxNz8cvThk4hg@mail.gmail.com> (raw)
In-Reply-To: <20170920142619.co2d6onsntz2ynjt@x230>
Hi Petr,
2017-09-20 23:26 GMT+09:00 Petr Vorel <petr.vorel@gmail.com>:
> Hi Masahiro,
>
>> Hi Petr,
>
>> 2017-04-03 18:35 GMT+09:00 Petr Vorel <pvorel@suse.cz>:
>> > Hi,
>
>> >> rev_dep expressions can get rather unwieldy, especially if a symbol is
>> >> selected by more than a handful of other symbols. Ie, it's possible to
>> >> have near endless expressions like:
>> >> A && B && !C || D || F && (G || H) || [...]
>
>> >> Chop these expressions into actually readable chunks:
>> >> - A && B && !C
>> >> - D
>> >> - F && (G || H)
>> >> - [...]
>
>> >> Ie, transform the top level "||" tokens into newlines and prepend each
>> >> line with a minus. This makes the "Selected by:" blurb much easier to
>> >> read.
>
>> >> This also prevents trimming too long lines.
>
>> >> Based on patch from Paul Bolle.
> <snip>
>
>> > Any comment on this patch, please?
>
>
>> I noticed you added me in the To: list.
> Thank you for your comments.
> I'm sorry, it took me rather long time to reply.
>
>> Basically I think this patch is a nice idea,
>> but I am not a Kconfig maintainer. Sorry.
>> (I could pick up a really trivial one via kbuild tree somehow,
>> but I want this one to be handled by a person with expertise in the area.)
>
>> Yann E. MORIN is the Kconfig maintainer, but he has been
>> silent for a few years. I guess Kconfig needs a new maintainer.
> Well, Yann is still listed in MAINTAINERS file, even he's inactive (according to the date
> of his git tree).
>
>
>> Please take my comment just as a Kconfig user's point of view.
>
>> The git-log only mentions "select", but I notice this patch
>> also changes "depends on" format in a bit different way.
>
>> For example,
>
>> General setup --->
>> Kernel compression mode (Gzip) --->
>
>
>> shows its help like this:
>
>> Depends on: HAVE_KERNEL_GZIP [=y]
>> - HAVE_KERNEL_BZIP2 [=n]
>> - HAVE_KERNEL_LZMA [=y]
>> - HAVE_KERNEL_XZ [=y]
>> - HAVE_KERNEL_LZO [=y]
>> - HAVE_KERNEL_LZ4 [=y]
>
>> (the first dependency in the same line in the "Depends on")
>
> You're right, I overlooked it. Do you think it makes sense use it also for "Depends on"
> section?
Yeah, I guess printing it in a consistent way will be better.
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2017-10-04 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 13:10 [PATCH v3 1/1] kconfig: menuconfig make "selected by:" readable Petr Vorel
2017-04-03 9:35 ` Petr Vorel
2017-04-10 16:01 ` Masahiro Yamada
2017-09-20 14:26 ` Petr Vorel
2017-09-20 16:38 ` Yann E. MORIN
2017-10-04 9:19 ` Masahiro Yamada
2017-10-04 9:18 ` Masahiro Yamada [this message]
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='CAK7LNASbFBSA=aQUkYVWBbSA9F7UHc2=GAoSFhxNz8cvThk4hg@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
--cc=petr.vorel@gmail.com \
--cc=pvorel@suse.cz \
--cc=yann.morin.1998@free.fr \
/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).