manpages: italicize command names
This includes nongit commands like RCS 'merge'. This patch only italicizes names of commands if they had no formatting before. Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonathan Nieder committed
Jul 3, 2008 at 00:37 UTC
0979c106498f21838140313b485f90faf06f454f
6 files changed
+11
-11
Documentation/config.txt
+2
-2
@@ -568,7 +568,7 @@ diff.external::
568
569
diff.renameLimit::
570
The number of files to consider when performing the copy/rename
571
- detection; equivalent to the git-diff option '-l'.
571
+ detection; equivalent to the 'git-diff' option '-l'.
572
573
diff.renames::
574
Tells git to detect renames. If set to any boolean value, it
@@ -844,7 +844,7 @@ instaweb.port::
844
845
log.date::
846
Set default date-time mode for the log command. Setting log.date
847
- value is similar to using git-log's --date option. The value is one of the
847
+ value is similar to using 'git-log'\'s --date option. The value is one of the
848
following alternatives: {relative,local,default,iso,rfc,short}.
849
See linkgit:git-log[1].
850
Documentation/git-apply.txt
+3
-3
@@ -18,7 +18,7 @@ SYNOPSIS
18
19
DESCRIPTION
20
-----------
21
-Reads supplied diff output and applies it on a git index file
21
+Reads supplied 'diff' output and applies it on a git index file
22
and a work tree.
23
24
OPTIONS
@@ -165,9 +165,9 @@ behavior:
165
* `error-all` is similar to `error` but shows all errors.
166
167
--inaccurate-eof::
168
- Under certain circumstances, some versions of diff do not correctly
168
+ Under certain circumstances, some versions of 'diff' do not correctly
169
detect a missing new-line at the end of the file. As a result, patches
170
- created by such diff programs do not record incomplete lines
170
+ created by such 'diff' programs do not record incomplete lines
171
correctly. This option adds support for applying such patches by
172
working around this bug.
173
Documentation/git-merge-file.txt
+1
-1
@@ -85,7 +85,7 @@ Written by Johannes Schindelin <johannes.schindelin@gmx.de>
85
Documentation
86
--------------
87
Documentation by Johannes Schindelin and the git-list <git@vger.kernel.org>,
88
-with parts copied from the original documentation of RCS merge.
88
+with parts copied from the original documentation of RCS 'merge'.
89
90
GIT
91
---
Documentation/git-merge-index.txt
+1
-1
@@ -41,7 +41,7 @@ processes them in turn only stopping if merge returns a non-zero exit
41
code.
42
43
Typically this is run with a script calling git's imitation of
44
-the merge command from the RCS package.
44
+the 'merge' command from the RCS package.
45
46
A sample script called `git-merge-one-file` is included in the
47
distribution.
Documentation/git-rerere.txt
+2
-2
@@ -7,7 +7,7 @@ git-rerere - Reuse recorded resolution of conflicted merges
7
8
SYNOPSIS
9
--------
10
-'git rerere' [clear|diff|status|gc]
10
+'git rerere' ['clear'|'diff'|'status'|'gc']
11
12
DESCRIPTION
13
-----------
@@ -49,7 +49,7 @@ conflicts. Additional arguments are passed directly to the system
49
50
'status'::
51
52
-Like diff, but this only prints the filenames that will be tracked
52
+Like 'diff', but this only prints the filenames that will be tracked
53
for resolutions.
54
55
'gc'::
Documentation/gitdiffcore.txt
+2
-2
@@ -7,7 +7,7 @@ gitdiffcore - Tweaking diff output (June 2005)
7
8
SYNOPSIS
9
--------
10
-git diff *
10
+'git diff' *
11
12
DESCRIPTION
13
-----------
@@ -16,7 +16,7 @@ The diff commands `git-diff-index`, `git-diff-files`, and `git-diff-tree`
16
can be told to manipulate differences they find in
17
unconventional ways before showing `diff` output. The manipulation
18
is collectively called "diffcore transformation". This short note
19
-describes what they are and how to use them to produce diff output
19
+describes what they are and how to use them to produce 'diff' output
20
that is easier to understand than the conventional kind.
21
22