manpages: italicize git subcommand names (which were in teletype font)
Italicize those git subcommand names already in teletype we missed. 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:59 UTC
5833d730efb7131bccbcdcab13ba56707629be2c
4 files changed
+10
-10
Documentation/config.txt
+4
-4
@@ -118,8 +118,8 @@ core.fileMode::
118
See linkgit:git-update-index[1]. True by default.
119
120
core.quotepath::
121
- The commands that output paths (e.g. `ls-files`,
122
- `diff`), when not given the `-z` option, will quote
121
+ The commands that output paths (e.g. 'ls-files',
122
+ 'diff'), when not given the `-z` option, will quote
123
"unusual" characters in the pathname by enclosing the
124
pathname in a double-quote pair and with backslashes the
125
same way strings in C source code are quoted. If this
@@ -557,7 +557,7 @@ diff.autorefreshindex::
557
contents in the work tree match the contents in the
558
index. This option defaults to true. Note that this
559
affects only 'git-diff' Porcelain, and not lower level
560
- `diff` commands, such as 'git-diff-files'.
560
+ 'diff' commands, such as 'git-diff-files'.
561
562
diff.external::
563
If this config variable is set, diff generation is not
@@ -636,7 +636,7 @@ gc.packrefs::
636
prevent `git pack-refs` from being run from 'git-gc'.
637
638
gc.pruneexpire::
639
- When 'git-gc' is run, it will call `prune --expire 2.weeks.ago`.
639
+ When 'git-gc' is run, it will call 'prune --expire 2.weeks.ago'.
640
Override the grace period with this config variable.
641
642
gc.reflogexpire::
Documentation/git-svn.txt
+1
-1
@@ -551,7 +551,7 @@ CAVEATS
551
552
For the sake of simplicity and interoperating with a less-capable system
553
(SVN), it is recommended that all 'git-svn' users clone, fetch and dcommit
554
-directly from the SVN server, and avoid all 'git-clone'/`pull`/`merge`/`push`
554
+directly from the SVN server, and avoid all 'git-clone'/'pull'/'merge'/'push'
555
operations between git repositories and branches. The recommended
556
method of exchanging code between git branches and users is
557
'git-format-patch' and 'git-am', or just 'dcommit'ing to the SVN repository.
Documentation/gitcore-tutorial.txt
+3
-3
@@ -235,7 +235,7 @@ $ git diff-files
235
------------
236
237
Oops. That wasn't very readable. It just spit out its own internal
238
-version of a `diff`, but that internal version really just tells you
238
+version of a 'diff', but that internal version really just tells you
239
that it has noticed that "hello" has been modified, and that the old object
240
contents it had have been replaced with something else.
241
@@ -468,7 +468,7 @@ Inspecting Changes
468
469
While creating changes is useful, it's even more useful if you can tell
470
later what changed. The most useful command for this is another of the
471
-`diff` family, namely 'git-diff-tree'.
471
+'diff' family, namely 'git-diff-tree'.
472
473
'git-diff-tree' can be given two arbitrary trees, and it will tell you the
474
differences between them. Perhaps even more commonly, though, you can
@@ -1006,7 +1006,7 @@ the tree of your branch to that of the `master` branch. This is
1006
often called 'fast forward' merge.
1007
1008
You can run `gitk \--all` again to see how the commit ancestry
1009
-looks like, or run `show-branch`, which tells you this.
1009
+looks like, or run 'show-branch', which tells you this.
1010
1011
------------------------------------------------
1012
$ git show-branch master mybranch
Documentation/gitcvs-migration.txt
+2
-2
@@ -46,7 +46,7 @@ them first before running git pull.
46
47
[NOTE]
48
================================
49
-The `pull` command knows where to get updates from because of certain
49
+The 'pull' command knows where to get updates from because of certain
50
configuration variables that were set by the first 'git-clone'
51
command; see `git config -l` and the linkgit:git-config[1] man
52
page for details.
@@ -67,7 +67,7 @@ push again.
67
In the 'git-push' command above we specify the name of the remote branch
68
to update (`master`). If we leave that out, 'git-push' tries to update
69
any branches in the remote repository that have the same name as a branch
70
-in the local repository. So the last `push` can be done with either of:
70
+in the local repository. So the last 'push' can be done with either of:
71
72
------------
73
$ git push origin