From: Paul Bolle <pebolle@tiscali.nl>
To: Michal Marek <mmarek@suse.cz>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] [RFC] kconfig: menuconfig make "Selected by:" readable
Date: Thu, 22 Jan 2015 11:47:34 +0100 [thread overview]
Message-ID: <1421923654.13638.56.camel@x220> (raw)
In-Reply-To: <54C0D1F3.6000001@suse.cz>
On Thu, 2015-01-22 at 11:33 +0100, Michal Marek wrote:
> On 2015-01-22 09:35, Paul Bolle wrote:
> > In this case 64BIT is set to 'y' (otherwise LBDAF would have been 'y').
> > This isn't a bug issue, of course, but I still can see how this can be
> > confusing. Perhaps the last line should read:
> > Unmet dependency on: BLOCK [=y] && !64BIT [=y]
> >
> > Would that help? Or would
> > Depends on: BLOCK [=y] && !64BIT [=n]
> >
> > (ie, print the value if "!64BIT") be clearer?
>
> How about
>
> Depends on: (BLOCK [=y] && !64BIT [=y]) [=n]
>
> ?
Or
Depends on: BLOCK [=y] && !64BIT [=y] => [=n]
Whatever, we'll figure out something.
This is a curses UI, isn't it? Could we use color to distinguish the
symbols or sub-expressions that are set correctly, for that particular
dependency, from those that are not?
Paul Bolle
next prev parent reply other threads:[~2015-01-22 10:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 23:00 [PATCH] [RFC] kconfig: menuconfig make "Selected by:" readable Paul Bolle
2015-01-22 2:23 ` Randy Dunlap
2015-01-22 8:35 ` Paul Bolle
2015-01-22 8:50 ` Paul Bolle
2015-01-22 10:33 ` Michal Marek
2015-01-22 10:47 ` Paul Bolle [this message]
2015-01-22 10:51 ` Michal Marek
2015-01-22 8:38 ` Paul Bolle
-- strict thread matches above, loose matches on Subject: below --
2015-05-18 21:19 Petr Vorel
2015-05-18 21:28 ` Paul Bolle
2015-05-19 4:06 ` Petr Vorel
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=1421923654.13638.56.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.