git/Documentation/gitk.txt, branch v1.6.4

Documentation: Expand a couple of abbreviations

2009-03-04T05:42:44Z

These may not be obvious to non-native English speakers Signed-off-by: Mike Ralphson Signed-off-by: Junio C Hamano

Documentation: clarify commits affected by gitk --merge

2009-02-09T05:21:28Z

Signed-off-by: Sitaram Chamarty Signed-off-by: Junio C Hamano

Merge branch 'maint' to sync with GIT 1.6.0.6

2008-12-20T03:35:55Z

Signed-off-by: Junio C Hamano

Documentation: fix typos, grammar, asciidoc syntax

2008-12-20T03:10:46Z

Signed-off-by: Markus Heidelberg Signed-off-by: Junio C Hamano

Documentation: New GUI configuration and command-line options.

2008-11-15T05:38:11Z

Add information on new git-gui and gitk command-line options, configuration variables, and the encoding attribute. Signed-off-by: Alexander Gavrilov Signed-off-by: Junio C Hamano

Document gitk --argscmd flag.

2008-08-29T07:14:29Z

This was part of my original patch, but appears to have been lost. Signed-off-by: Yann Dirson Signed-off-by: Junio C Hamano

Make the DESCRIPTION match ... items in the SYNOPSIS

2008-07-31T04:42:55Z

When the SYNOPSIS says e.g. "...", it is nice if the DESCRIPTION also mentions "..." and says the specified "paths" (note plural) are used for $whatever. This fixes the obvious mismatches. Signed-off-by: Abhijit Menon-Sen Signed-off-by: Junio C Hamano

manpages: italicize git command names (which were in teletype font)

2008-07-05T18:24:40Z

The names of git commands are not meant to be entered at the commandline; they are just names. So we render them in italics, as is usual for command names in manpages. Using doit () { perl -e 'for (<>) { s/\`(git-[^\`.]*)\`/'\''\1'\''/g; print }' } for i in git*.txt config.txt diff*.txt blame*.txt fetch*.txt i18n.txt \ merge*.txt pretty*.txt pull*.txt rev*.txt urls*.txt do doit <"$i" >"$i+" && mv "$i+" "$i" done git diff . Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano

Documentation formatting and cleanup

2008-07-02T00:20:16Z

Following what appears to be the predominant style, format names of commands and commandlines both as `teletype text`. While we're at it, add articles ("a" and "the") in some places, italicize the name of the command in the manual page synopsis line, and add a comma or two where it seems appropriate. Signed-off-by: Jonathan Nieder Signed-off-by: Junio C Hamano

Docs: Use "-l::\n--long\n" format in OPTIONS sections

2008-06-08T20:46:38Z

The OPTIONS section of a documentation file contains a list of the options a git command accepts. Currently there are several variants to describe the case that different options (almost) do the same in the OPTIONS section. Some are: -f, --foo:: -f|--foo:: -f | --foo:: But AsciiDoc has the special form: -f:: --foo:: This patch applies this form to the documentation of the whole git suite, and removes useless em-dash prevention, so \--foo becomes --foo. Signed-off-by: Stephan Beyer Signed-off-by: Junio C Hamano