diff options
| author | Junio C Hamano <gitster@pobox.com> | 2015-08-03 18:01:24 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2015-08-03 18:01:24 (GMT) |
| commit | 2bf2d819e1ccd4865500e957cc5953de31255c46 (patch) | |
| tree | defd94f473ca2099749e9956777b405539bcb2b5 /Documentation | |
| parent | 3ecca8879a07889884dcdc90066c76c4e948856a (diff) | |
| parent | 2d893dff4c3c49750557da7a1701b46c1fe95844 (diff) | |
| download | git-2bf2d819e1ccd4865500e957cc5953de31255c46.zip git-2bf2d819e1ccd4865500e957cc5953de31255c46.tar.gz git-2bf2d819e1ccd4865500e957cc5953de31255c46.tar.bz2 | |
Merge branch 'ib/scripted-parse-opt-better-hint-string'
The "rev-parse --parseopt" mode parsed the option specification
and the argument hint in a strange way to allow '=' and other
special characters in the option name while forbidding them from
the argument hint. This made it impossible to define an option
like "--pair <key>=<value>" with "pair=key=value" specification,
which instead would have defined a "--pair=key <value>" option.
* ib/scripted-parse-opt-better-hint-string:
rev-parse --parseopt: allow [*=?!] in argument hints
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/git-rev-parse.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt index c483100..b6c6326 100644 --- a/Documentation/git-rev-parse.txt +++ b/Documentation/git-rev-parse.txt @@ -311,8 +311,8 @@ Each line of options has this format: `<opt-spec>`:: its format is the short option character, then the long option name separated by a comma. Both parts are not required, though at least one - is necessary. `h,help`, `dry-run` and `f` are all three correct - `<opt-spec>`. + is necessary. May not contain any of the `<flags>` characters. + `h,help`, `dry-run` and `f` are examples of correct `<opt-spec>`. `<flags>`:: `<flags>` are of `*`, `=`, `?` or `!`. |