manpages: italicize gitk's name (where it was in teletype font)
The name `gitk` is sometimes meant to be entered at the command prompt, but most uses are just referring to the program with that name (not the incantation to start it). 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:49 UTC
42d36bb841eb035eb0f7261f02987893c14e1a02
4 files changed
+5
-5
Documentation/git-bisect.txt
+1
-1
@@ -98,7 +98,7 @@ During the bisection process, you can say
98
$ git bisect visualize
99
------------
100
101
-to see the currently remaining suspects in `gitk`. `visualize` is a bit
101
+to see the currently remaining suspects in 'gitk'. `visualize` is a bit
102
too long to type and `view` is provided as a synonym.
103
104
If 'DISPLAY' environment variable is not set, 'git-log' is used
Documentation/git-gui.txt
+2
-2
@@ -16,9 +16,9 @@ on allowing users to make changes to their repository by making
16
new commits, amending existing ones, creating branches, performing
17
local merges, and fetching/pushing to remote repositories.
18
19
-Unlike `gitk`, 'git-gui' focuses on commit generation
19
+Unlike 'gitk', 'git-gui' focuses on commit generation
20
and single file annotation and does not show project history.
21
-It does however supply menu actions to start a `gitk` session from
21
+It does however supply menu actions to start a 'gitk' session from
22
within 'git-gui'.
23
24
'git-gui' is known to work on all popular UNIX systems, Mac OS X,
Documentation/gitcore-tutorial.txt
+1
-1
@@ -878,7 +878,7 @@ means: normally it will just show you your current `HEAD`) and their
878
histories. You can also see exactly how they came to be from a common
879
source.
880
881
-Anyway, let's exit `gitk` (`^Q` or the File menu), and decide that we want
881
+Anyway, let's exit 'gitk' (`^Q` or the File menu), and decide that we want
882
to merge the work we did on the `mybranch` branch into the `master`
883
branch (which is currently our `HEAD` too). To do that, there's a nice
884
script called 'git-merge', which wants to know which branches you want
Documentation/gittutorial.txt
+1
-1
@@ -529,7 +529,7 @@ then merged back together, the order in which 'git-log' presents
529
those commits is meaningless.
530
531
Most projects with multiple contributors (such as the linux kernel,
532
-or git itself) have frequent merges, and `gitk` does a better job of
532
+or git itself) have frequent merges, and 'gitk' does a better job of
533
visualizing their history. For example,
534
535
-------------------------------------