manpages: use teletype font for sample command lines

I think that some of these uses of italics were meant to be
rendered in quotation marks, anyway.

Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

diff --git a/Documentation/git-gui.txt b/Documentation/git-gui.txt
index a73201d933aa37bdf7cadcfeef3c8a1e42b3e2ec..0e650f497bd456e633334a91bd929053a08eb0d3 100644 (file)
--- a/Documentation/git-gui.txt
+++ b/Documentation/git-gui.txt
@@ -71,7 +71,7 @@ git gui citool::
 
 git citool::
 
 
 git citool::
 

-       Same as 'git gui citool' (above).
+       Same as `git gui citool` (above).

 
 git gui browser maint::
 
 
 git gui browser maint::
 

diff --git a/Documentation/git-help.txt b/Documentation/git-help.txt
index d5b20f88f4918bf7f260faccbcec76607d1345c4..f414583fc48e85e4785fbf5f9431bb81a96ccd9d 100644 (file)
--- a/Documentation/git-help.txt
+++ b/Documentation/git-help.txt
@@ -23,7 +23,7 @@ If a git command is named, a manual page for that command is brought
 up. The 'man' program is used by default for this purpose, but this
 can be overridden by other options or configuration variables.
 
 up. The 'man' program is used by default for this purpose, but this
 can be overridden by other options or configuration variables.
 

-Note that 'git --help ...' is identical as 'git help ...' because the
+Note that `git --help ...` is identical to `git help ...` because the

 former is internally converted into the latter.
 
 OPTIONS
 former is internally converted into the latter.
 
 OPTIONS

diff --git a/Documentation/git-reflog.txt b/Documentation/git-reflog.txt
index 1710626cfa8dd9ae92ef10b7fe40e0c372419cbd..146d7f545cb2f85177c8143b7e7b999ae8303d71 100644 (file)
--- a/Documentation/git-reflog.txt
+++ b/Documentation/git-reflog.txt
@@ -36,7 +36,7 @@ The subcommand "show" (which is also the default, in the absence of any
 subcommands) will take all the normal log options, and show the log of
 the reference provided in the command-line (or `HEAD`, by default).
 The reflog will cover all recent actions (HEAD reflog records branch switching
 subcommands) will take all the normal log options, and show the log of
 the reference provided in the command-line (or `HEAD`, by default).
 The reflog will cover all recent actions (HEAD reflog records branch switching

-as well).  It is an alias for 'git log -g --abbrev-commit --pretty=oneline';
+as well).  It is an alias for `git log -g --abbrev-commit --pretty=oneline`;

 see linkgit:git-log[1].
 
 The reflog is useful in various git commands, to specify the old value
 see linkgit:git-log[1].
 
 The reflog is useful in various git commands, to specify the old value


@@ -46,7 +46,7 @@ point to one week ago", and so on. See linkgit:git-rev-parse[1] for
 more details.
 
 To delete single entries from the reflog, use the subcommand "delete"
 more details.
 
 To delete single entries from the reflog, use the subcommand "delete"

-and specify the _exact_ entry (e.g. ``git reflog delete master@\{2\}'').
+and specify the _exact_ entry (e.g. "`git reflog delete master@\{2\}`").

 
 
 OPTIONS
 
 
 OPTIONS

diff --git a/Documentation/git.txt b/Documentation/git.txt
index 07e9e57c5836fe1409381c491ff6b13962d392ae..adc027ce499eee277138309c9234e35f4b0dc433 100644 (file)
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -136,8 +136,8 @@ OPTIONS
 +
 Other options are available to control how the manual page is
 displayed. See linkgit:git-help[1] for more information,
 +
 Other options are available to control how the manual page is
 displayed. See linkgit:git-help[1] for more information,

-because 'git --help ...' is converted internally into 'git
-help ...'.
+because `git --help ...` is converted internally into `git
+help ...`.

 
 --exec-path::
        Path to wherever your core git programs are installed.
 
 --exec-path::
        Path to wherever your core git programs are installed.

diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
index dd6a26827fe0719d9f184fff91cba9e2b917d1ea..a2b92933f734734cbc4bfe60987724fac47ecbdd 100644 (file)
--- a/Documentation/gitcore-tutorial.txt
+++ b/Documentation/gitcore-tutorial.txt
@@ -1655,7 +1655,7 @@ branch before these two merges by resetting it to 'master~2':
 $ git reset --hard master~2
 ------------
 
 $ git reset --hard master~2
 ------------
 

-You can make sure 'git show-branch' matches the state before
+You can make sure `git show-branch` matches the state before

 those two 'git-merge' you just did.  Then, instead of running
 two 'git-merge' commands in a row, you would merge these two
 branch heads (this is known as 'making an Octopus'):
 those two 'git-merge' you just did.  Then, instead of running
 two 'git-merge' commands in a row, you would merge these two
 branch heads (this is known as 'making an Octopus'):