From: Eugeniu Rosca <roscaeugeniu@gmail.com>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Ulf Magnusson <ulfalizer@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Randy Dunlap <rdunlap@infradead.org>,
Paul Bolle <pebolle@tiscali.nl>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Eugeniu Rosca <rosca.eugeniu@gmail.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>
Subject: Re: [PATCH 2/2] kconfig: Print the value of each reverse dependency
Date: Sat, 17 Feb 2018 18:26:30 +0100 [thread overview]
Message-ID: <20180217172630.GB16512@example.com> (raw)
In-Reply-To: <20180214004153.GA1154@x230>
Hello Petr,
On Wed, Feb 14, 2018 at 01:41:54AM +0100, Petr Vorel wrote:
> Hi Eugeniu,
>
> > To be honest, purely as a user, I would probably prefer something like
> > below:
>
> > Selected by [y/m]:
> > - EXPR_01
> > - EXPR_02
> > Selected by [n]:
> > - EXPR_03
> > - EXPR_04
> Sorting again, just with header? It looks more readable (although Masahiro's approach is
> quite readable as well). If you chose this, I'd suggest not displaying title, when there
> is empty list. i.e., don't show "Selected by [y/m]" in this:
> Selected by [y/m]:
> Selected by [n]:
> - EXPR_03
> - EXPR_04
I took your preference into consideration in the v3 revision. Thanks!
Best regards,
Eugeniu.
next prev parent reply other threads:[~2018-02-17 17:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 0:56 [PATCH 1/2] kconfig: Print reverse dependencies on new line consistently Eugeniu Rosca
2018-02-13 0:56 ` [PATCH 2/2] kconfig: Print the value of each reverse dependency Eugeniu Rosca
2018-02-13 6:18 ` Ulf Magnusson
2018-02-13 23:54 ` Eugeniu Rosca
2018-02-14 0:41 ` Petr Vorel
2018-02-17 17:26 ` Eugeniu Rosca [this message]
2018-02-14 4:09 ` Ulf Magnusson
2018-02-17 17:20 ` Eugeniu Rosca
2018-02-17 17:31 ` Ulf Magnusson
2018-02-18 11:34 ` Eugeniu Rosca
2018-02-14 0:46 ` Petr Vorel
2018-02-13 6:11 ` [PATCH 1/2] kconfig: Print reverse dependencies on new line consistently Ulf Magnusson
2018-02-13 6:40 ` Petr Vorel
2018-02-14 0:32 ` Eugeniu Rosca
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=20180217172630.GB16512@example.com \
--to=roscaeugeniu@gmail.com \
--cc=erosca@de.adit-jv.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=pebolle@tiscali.nl \
--cc=petr.vorel@gmail.com \
--cc=rdunlap@infradead.org \
--cc=rosca.eugeniu@gmail.com \
--cc=ulfalizer@gmail.com \
--cc=yamada.masahiro@socionext.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