From: Michael Haggerty Date: Thu, 18 Apr 2013 07:46:35 GMT Subject: [PATCH 2/2] api-parse-options.txt: document "no-" for non-boolean options Message-ID: <1366271195-4276-3-git-send-email-mhagger@alum.mit.edu> In-Reply-To: <1366271195-4276-1-git-send-email-mhagger@alum.mit.edu> Document that the "no-" prefix can also be used for non-boolean options. Signed-off-by: Michael Haggerty --- Documentation/technical/api-parse-options.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/technical/api-parse-options.txt b/Documentation/technical/api-parse-options.txt index 32ddc1c..2ff368e 100644 --- a/Documentation/technical/api-parse-options.txt +++ b/Documentation/technical/api-parse-options.txt @@ -41,6 +41,8 @@ The parse-options API allows: * Boolean long options can be 'negated' (or 'unset') by prepending `no-`, e.g. `--no-abbrev` instead of `--abbrev`. Conversely, options that begin with `no-` can be 'negated' by removing it. + Other long options can be unset (e.g., set string to NULL, set + integer to 0) by prepending `no-`. * Options and non-option arguments can clearly be separated using the `--` option, e.g. `-a -b --option -- --this-is-a-file` indicates that -- 1.8.2.1