lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 4 May 2007 09:46:22 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Trent Piepho <xyzzy@...akeasy.org>
cc:	Roman Zippel <zippel@...ux-m68k.org>,
	Sam Ravnborg <sam@...nborg.org>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	v4l-dvb maintainer list <v4l-dvb-maintainer@...uxtv.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH 35/36] Use menuconfig objects II -
 DVB


On May 3 2007 18:40, Trent Piepho wrote:
>
>How about these examples:
>
>menuconfig FOO
>if FOO
>config A
>	depends on FOO
>endif
>config B
>if FOO
>config C
>	depends on FOO
>endif

This does not work as expected in ncurses-menuconfig either.
It does not even need a "menuconfig" object for that, something
as simple as

config A
config B
config C
  depends on A

prints it

A
B
C

rather than

A
\_ C
B

which is why some of my menuconfig patches _move_ C to not come after B.

>How does it show the first one, keeping the config entries in the correct
>order and put them into the menu at the same time?
>
>And which of what should the second be show?
>
>foo
>\-bar
>  \-baz
>
>or
>
>foo
>|-bar
>\-baz
>
>There is no question with menus, as the menu tree is clearly lexically
>defined by the matching menu / endmenu pairs.  But menuconfig doesn't work
>that way, and it seems like it would make more sense if it did.
>

Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ