| commit | d3ac359841969199397c36b4085ca3afd527b4d5 | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Wed, 19 Aug 2015 21:41:29 +0000 (19 14:41 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 19 Aug 2015 21:41:29 +0000 (19 14:41 -0700) | ||
| tree | ca6e636d7e5b45d2dec404c62fde79584ae7aafe | treesnapshot (tar.gz zip) |
| parent | 204ea3cad443df4f14623a09ee8201a552f067af | commitdiff |
| parent | 2d893dff4c3c49750557da7a1701b46c1fe95844 | commitdiff |
Merge branch 'ib/scripted-parse-opt-better-hint-string' into maint
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
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