Many flag options are boolean and support both a positive and a negative invocation from the command line. Some of these are even mentioned by example (e.g., --nogit is mentioned as a default option), but they aren't explicitly mentioned in the list of options. It happens that some of these are pretty important, as they are default-on, and to turn them off, you have to know about the --no-foo version.
Rather than clutter the whole help text with bracketed '--[no]foo', let's just mention the general rule, a la 'man gcc'. Signed-off-by: Brian Norris <[email protected]> Cc: Andrew Morton <[email protected]> Cc: Joe Perches <[email protected]> --- v1 -> v2: * don't clutter with --[no]foo bracketing; just include this note up front; suggested by Joe v1: https://lkml.org/lkml/2015/8/19/441 scripts/get_maintainer.pl | 3 +++ 1 file changed, 3 insertions(+) diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl index 6c307276f3d6..13115eab8992 100755 --- a/scripts/get_maintainer.pl +++ b/scripts/get_maintainer.pl @@ -770,6 +770,9 @@ usage: $P [options] patchfile $P [options] -f file|directory version: $V +Most options have both positive and negative forms. The negative form of --foo +is --nofoo. + MAINTAINER field selection options: --email => print email address(es) if any --git => include recent git \*-by: signers -- 2.6.0.rc2.230.g3dd15c0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
