summaryrefslogtreecommitdiff
path: root/menuconfig.py
diff options
context:
space:
mode:
authorUlf Magnusson <ulfalizer@gmail.com>2018-11-28 15:34:52 +0100
committerUlf Magnusson <ulfalizer@gmail.com>2018-11-28 15:37:50 +0100
commit3d9217b5c021f5bd8e35b09eedfba8121aa051b1 (patch)
treef56c9b02e782da22fb89766ab627f1016462f769 /menuconfig.py
parent38dff36b0f97b8c87bc95f18fce2c8d7d5a860d5 (diff)
menuconfig: Clarify the scope of the named choice special-casing
One thing that irks me a bit about it is that it might give the idea that menuconfigs have to include it, making things seem more complex than they really are.
Diffstat (limited to 'menuconfig.py')
-rwxr-xr-xmenuconfig.py3
1 files changed, 3 insertions, 0 deletions
diff --git a/menuconfig.py b/menuconfig.py
index 2d4c367..fd36abe 100755
--- a/menuconfig.py
+++ b/menuconfig.py
@@ -1421,6 +1421,9 @@ def _shown_nodes(menu):
#
# Note: Named choices are pretty broken in the C tools, and this is
# super obscure, so you probably won't find much that relies on this.
+ # This whole 'if' could be deleted if you don't care about defining
+ # choices in multiple locations to add symbols (which will still work,
+ # just with things being displayed in a way that might be unexpected).
# Do some additional work to avoid listing choice symbols twice if all
# or part of the choice is copied in multiple locations (e.g. by