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>

diff --git a/Documentation/config.txt b/Documentation/config.txt
index f7a54f65b04c5eff5e75328a3a48e8e1e9724806..a403d46c1ba3068abe5c0583533de651f6116fd4 100644 (file)
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -118,8 +118,8 @@ core.fileMode::
        See linkgit:git-update-index[1]. True by default.
 
 core.quotepath::
        See linkgit:git-update-index[1]. True by default.
 
 core.quotepath::

-       The commands that output paths (e.g. `ls-files`,
-       `diff`), when not given the `-z` option, will quote
+       The commands that output paths (e.g. 'ls-files',
+       'diff'), when not given the `-z` option, will quote

        "unusual" characters in the pathname by enclosing the
        pathname in a double-quote pair and with backslashes the
        same way strings in C source code are quoted.  If this
        "unusual" characters in the pathname by enclosing the
        pathname in a double-quote pair and with backslashes the
        same way strings in C source code are quoted.  If this


@@ -557,7 +557,7 @@ diff.autorefreshindex::
        contents in the work tree match the contents in the
        index.  This option defaults to true.  Note that this
        affects only 'git-diff' Porcelain, and not lower level
        contents in the work tree match the contents in the
        index.  This option defaults to true.  Note that this
        affects only 'git-diff' Porcelain, and not lower level

-       `diff` commands, such as 'git-diff-files'.
+       'diff' commands, such as 'git-diff-files'.

 
 diff.external::
        If this config variable is set, diff generation is not
 
 diff.external::
        If this config variable is set, diff generation is not


@@ -636,7 +636,7 @@ gc.packrefs::
        prevent `git pack-refs` from being run from 'git-gc'.
 
 gc.pruneexpire::
        prevent `git pack-refs` from being run from 'git-gc'.
 
 gc.pruneexpire::

-       When 'git-gc' is run, it will call `prune --expire 2.weeks.ago`.
+       When 'git-gc' is run, it will call 'prune --expire 2.weeks.ago'.

        Override the grace period with this config variable.
 
 gc.reflogexpire::
        Override the grace period with this config variable.
 
 gc.reflogexpire::

diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index dc5b8f6c8403e9a58bd2d88d76fc43e152864f89..e7c0f1c959d39739e177096875dd8aac5fd185d9 100644 (file)
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -551,7 +551,7 @@ CAVEATS
 
 For the sake of simplicity and interoperating with a less-capable system
 (SVN), it is recommended that all 'git-svn' users clone, fetch and dcommit
 
 For the sake of simplicity and interoperating with a less-capable system
 (SVN), it is recommended that all 'git-svn' users clone, fetch and dcommit

-directly from the SVN server, and avoid all 'git-clone'/`pull`/`merge`/`push`
+directly from the SVN server, and avoid all 'git-clone'/'pull'/'merge'/'push'

 operations between git repositories and branches.  The recommended
 method of exchanging code between git branches and users is
 'git-format-patch' and 'git-am', or just 'dcommit'ing to the SVN repository.
 operations between git repositories and branches.  The recommended
 method of exchanging code between git branches and users is
 'git-format-patch' and 'git-am', or just 'dcommit'ing to the SVN repository.

diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
index 5acdeb7b8bef58d5a5791fa9d16a385bbc8396ff..dd6a26827fe0719d9f184fff91cba9e2b917d1ea 100644 (file)
--- a/Documentation/gitcore-tutorial.txt
+++ b/Documentation/gitcore-tutorial.txt
@@ -235,7 +235,7 @@ $ git diff-files
 ------------
 
 Oops. That wasn't very readable. It just spit out its own internal
 ------------
 
 Oops. That wasn't very readable. It just spit out its own internal

-version of a `diff`, but that internal version really just tells you
+version of a 'diff', but that internal version really just tells you

 that it has noticed that "hello" has been modified, and that the old object
 contents it had have been replaced with something else.
 
 that it has noticed that "hello" has been modified, and that the old object
 contents it had have been replaced with something else.
 


@@ -468,7 +468,7 @@ Inspecting Changes
 
 While creating changes is useful, it's even more useful if you can tell
 later what changed. The most useful command for this is another of the
 
 While creating changes is useful, it's even more useful if you can tell
 later what changed. The most useful command for this is another of the

-`diff` family, namely 'git-diff-tree'.
+'diff' family, namely 'git-diff-tree'.

 
 'git-diff-tree' can be given two arbitrary trees, and it will tell you the
 differences between them. Perhaps even more commonly, though, you can
 
 'git-diff-tree' can be given two arbitrary trees, and it will tell you the
 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
 often called 'fast forward' merge.
 
 You can run `gitk \--all` again to see how the commit ancestry
 often called 'fast forward' merge.
 
 You can run `gitk \--all` again to see how the commit ancestry

-looks like, or run `show-branch`, which tells you this.
+looks like, or run 'show-branch', which tells you this.

 
 ------------------------------------------------
 $ git show-branch master mybranch
 
 ------------------------------------------------
 $ git show-branch master mybranch

diff --git a/Documentation/gitcvs-migration.txt b/Documentation/gitcvs-migration.txt
index 2737d10aad1f0663eafe3ef3235be71a86c9f709..2eb6972a93f1033281b79fe03af6d80c06d576dc 100644 (file)
--- a/Documentation/gitcvs-migration.txt
+++ b/Documentation/gitcvs-migration.txt
@@ -46,7 +46,7 @@ them first before running git pull.
 
 [NOTE]
 ================================
 
 [NOTE]
 ================================

-The `pull` command knows where to get updates from because of certain
+The 'pull' command knows where to get updates from because of certain

 configuration variables that were set by the first 'git-clone'
 command; see `git config -l` and the linkgit:git-config[1] man
 page for details.
 configuration variables that were set by the first 'git-clone'
 command; see `git config -l` and the linkgit:git-config[1] man
 page for details.


@@ -67,7 +67,7 @@ push again.
 In the 'git-push' command above we specify the name of the remote branch
 to update (`master`).  If we leave that out, 'git-push' tries to update
 any branches in the remote repository that have the same name as a branch
 In the 'git-push' command above we specify the name of the remote branch
 to update (`master`).  If we leave that out, 'git-push' tries to update
 any branches in the remote repository that have the same name as a branch

-in the local repository.  So the last `push` can be done with either of:
+in the local repository.  So the last 'push' can be done with either of:

 
 ------------
 $ git push origin
 
 ------------
 $ git push origin