git/Documentation/git-bisect.txt, branch v2.22.2

Merge branch 'ak/bisect-doc-typofix'

2018-04-25T04:28:56Z

Docfix. * ak/bisect-doc-typofix: Documentation/git-bisect.txt: git bisect term → git bisect terms

Documentation/git-bisect.txt: git bisect term → git bisect terms

2018-04-07T11:50:19Z

Signed-off-by: Anders Kaseorg Signed-off-by: Junio C Hamano

bisect: mention "view" as an alternative to "visualize"

2017-11-13T01:51:14Z

Tweak a small number of files to mention "view" as an alternative to "visualize". Signed-off-by: Robert P. J. Day Signed-off-by: Junio C Hamano

git-bisect.txt: add missing word

2017-04-01T18:35:45Z

Signed-off-by: Quentin Pradet Signed-off-by: Junio C Hamano

Merge branch 'ad/bisect-terms'

2017-01-23T23:59:22Z

Documentation fix. * ad/bisect-terms: Documentation/bisect: improve on (bad|new) and (good|bad)

Documentation/bisect: improve on (bad|new) and (good|bad)

2017-01-13T19:15:38Z

The following part of the description: git bisect (bad|new) [] git bisect (good|old) [...] may be a bit confusing, as a reader may wonder if instead it should be: git bisect (bad|good) [] git bisect (old|new) [...] Of course the difference between "[]" and "[...]" should hint that there is a good reason for the way it is. But we can further clarify and complete the description by adding "" and "" to the "bad|new" and "good|old" alternatives. Signed-off-by: Christian Couder Signed-off-by: Junio C Hamano

doc: typeset HEAD and variants as literal

2016-06-28T15:36:45Z

This is an application of the newly added CodingGuidelines to HEAD and variants like FETCH_HEAD. It was obtained with: perl -pi -e "s/'([A-Z_]*HEAD)'/\`\$1\`/g" *.txt Signed-off-by: Matthieu Moy Signed-off-by: Junio C Hamano

doc: more consistency in environment variables format

2016-06-08T19:04:37Z

Wrap with backticks (monospaced font) unwrapped or single-quotes wrapped (italic type) environment variables which are followed by the word "environment". It was obtained with: perl -pi -e "s/\'?(\\\$?[0-9A-Z\_]+)\'?(?= environment ?)/\`\1\`/g" *.txt One of the main purposes is to stick to the CodingGuidelines as possible so that people writting new documentation by mimicking the existing are more likely to have it right (even if they didn't read the CodingGuidelines). Signed-off-by: Tom Russello Signed-off-by: Erwan Mathoniere Signed-off-by: Samuel Groot Signed-off-by: Matthieu Moy Reviewed-by: Matthieu Moy Signed-off-by: Junio C Hamano

Merge branch 'jc/em-dash-in-doc'

2015-10-29T20:59:16Z

AsciiDoc markup fixes. * jc/em-dash-in-doc: Documentation: AsciiDoc spells em-dash as double-dashes, not triple

Merge branch 'xf/user-manual-markup'

2015-10-29T20:59:14Z

AsciiDoc markup fixes. * xf/user-manual-markup: Documentation: match undefline with the text in old release notes Documentation: match underline with the text Documentation: fix header markup