John Levon asks: > why bother ? Anyone using this needs to read man readprofile anyway.
So then the help text should mention "man readprofile". Why bother? Because the use case is not someone who knows about profiling. The use case is someone who sees this boolean option appear on the screen and does not know whether they should use it or not. It bothers me a lot to see these options come up and see people claim that such-and-such should not be documented. ESR's list comes from the set of things that users see. Thus, everything on the list will have *some* text appear in response to the "?" button, even if it is "help: no help available". Linux is an OS by hackers, for hackers, and it's part of our culture to share information. If an option is a historical relic and connected to nothing, say so. If an option is very new and is not used yet because someone's tree isn't merged at this time, say so. If an option has a typo in its name and is about to be renamed -- say so. Document the system with truth and openness, and use tools to check that the set of options is current. Michael C _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
