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

Documentation: typofixes

2014-11-04T21:14:44Z

In addition to fixing trivial and obvious typos, be careful about the following points: - Spell ASCII, URL and CRC in ALL CAPS; - Spell Linux as Capitalized; - Do not omit periods in "i.e." and "e.g.". Signed-off-by: Thomas Ackermann Signed-off-by: Junio C Hamano

Documentation: a note about stdout for git rev-parse --verify --quiet

2014-09-15T22:34:31Z

Signed-off-by: David Aguilar Signed-off-by: Junio C Hamano

Sync with maint

2014-07-22T18:00:23Z

* maint: Documentation: fix missing text for rev-parse --verify

Merge branch 'maint-1.9' into maint

2014-07-22T17:17:34Z

* maint-1.9: Documentation: fix missing text for rev-parse --verify

Merge branch 'maint-1.8.5' into maint-1.9

2014-07-22T17:16:50Z

* maint-1.8.5: Documentation: fix missing text for rev-parse --verify

Documentation: fix missing text for rev-parse --verify

2014-07-22T17:10:57Z

The caret (^) is used as a markup symbol in AsciiDoc. Due to the inability of AsciiDoc to parse a line containing an unmatched caret, it omitted the line from the output, resulting in the man page missing the end of a sentence. Escape this caret so that the man page ends up with the complete text. Signed-off-by: brian m. carlson Signed-off-by: Junio C Hamano

rev-parse: add --shared-index-path to get shared index path

2014-06-13T18:49:41Z

Normally scripts do not have to be aware about split indexes because all shared indexes are in $GIT_DIR. A simple "mv $tmp_index $GIT_DIR/somewhere" is enough. Scripts that generate temporary indexes and move them across repos must be aware about split index and copy the shared file as well. This option enables that. Signed-off-by: Nguyễn Thái Ngọc Duy Signed-off-by: Junio C Hamano

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