git/Documentation/git-rev-parse.txt, branch v2.0.2

Merge branch 'ib/rev-parse-parseopt-argh'

2014-04-08T19:00:09Z

Finishing touch to a new topic scheduled for 2.0. * ib/rev-parse-parseopt-argh: rev-parse: fix typo in example on manpage

rev-parse: fix typo in example on manpage

2014-04-01T21:07:46Z

Signed-off-by: Junio C Hamano

parse-options: multi-word argh should use dash to separate words

2014-03-24T17:43:34Z

"When you need to use space, use dash" is a strange way to say that you must not use a space. Because it is more common for the command line descriptions to use dashed-multi-words, you do not even want to use spaces in these places. Rephrase the documentation to avoid this strangeness. Fix a few existing multi-word argument help strings, i.e. - GPG key-ids given to -S/--gpg-sign are "key-id"; - Refs used for storing notes are "notes-ref"; and - Expiry timestamps given to --expire are "expiry-date". and update the corresponding documentation pages. Signed-off-by: Junio C Hamano

rev-parse --parseopt: option argument name hints

2014-03-24T00:28:03Z

Built-in commands can specify names for option arguments when usage text is generated for a command. sh based commands should be able to do the same. Option argument name hint is any text that comes after [*=?!] after the argument name up to the first whitespace. Signed-off-by: Ilya Bobyr Signed-off-by: Junio C Hamano

Merge branch 'jc/ref-excludes'

2013-12-05T20:59:09Z

People often wished a way to tell "git log --branches" (and "git log --remotes --not --branches") to exclude some local branches from the expansion of "--branches" (similarly for "--tags", "--all" and "--glob="). Now they have one. * jc/ref-excludes: rev-parse: introduce --exclude= to tame wildcards rev-list --exclude: export add/clear-ref-exclusion and ref-excluded API rev-list --exclude: tests document --exclude option revision: introduce --exclude= to tame wildcards

rev-parse: introduce --exclude= to tame wildcards

2013-11-01T20:09:45Z

Teach "rev-parse" the same "I'm going to glob, but omit the ones that match these patterns" feature as "rev-list". Signed-off-by: Junio C Hamano

rev-parse --parseopt: add the --stuck-long mode

2013-10-31T22:47:41Z

Add the --stuck-long option to output the options in their long form if available, and with their arguments stuck. Contrary to the default form (non stuck arguments and short options), this can be parsed unambiguously when using options with optional arguments : - in the non stuck form, when an option is taking an optional argument you cannot know if the next argument is its optional argument, or the next option. - the long options form allows to differentiate between an empty argument '--option=' and an unset argument '--option', which is not possible with short options. Signed-off-by: Nicolas Vigier Signed-off-by: Junio C Hamano

Merge branch 'rj/doc-rev-parse'

2013-08-30T17:08:13Z

* rj/doc-rev-parse: rev-parse(1): logically group options rev-parse: remove restrictions on some options

typofix: documentation

2013-07-22T23:06:48Z

Signed-off-by: Ondřej Bílka Signed-off-by: Junio C Hamano

rev-parse(1): logically group options

2013-07-22T17:43:21Z

The options section of the git-rev-parse manual page has grown organically so that there now does not seem to be much logic behind the ordering of the options. It also does not make it clear that certain options must appear first on the command line. Address this by reorganising the options into groups with subheadings. The text of option descriptions does not change. Signed-off-by: John Keeping Signed-off-by: Junio C Hamano