summaryrefslogtreecommitdiff
path: root/Documentation/git-fsck.txt
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@uchicago.edu>2008-07-03 00:55:07 -0500
committerJunio C Hamano <gitster@pobox.com>2008-07-05 11:24:40 -0700
commit2fd02c92dbb6e575b7e62ea9dfa85ef45ebe58b6 (patch)
tree36245e4f2c047fe68d7af66fd6b9c2619d2c6762 /Documentation/git-fsck.txt
parent42d36bb841eb035eb0f7261f02987893c14e1a02 (diff)
downloadgit-2fd02c92dbb6e575b7e62ea9dfa85ef45ebe58b6.tar.gz
manpages: italicize nongit command names (if they are in teletype font)
Some manual pages use teletype font to set command names. We change them to use italics, instead. This creates a visual distinction between names of commands and command lines that can be typed at the command line. It is also more consistent with other man pages outside Git. In this patch, the commands named are non-git commands like bash. Signed-off-by: Jonathan Nieder <jrnieder@uchicago.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-fsck.txt')
-rw-r--r--Documentation/git-fsck.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-fsck.txt b/Documentation/git-fsck.txt
index 524e0b1c6f..d5a7647219 100644
--- a/Documentation/git-fsck.txt
+++ b/Documentation/git-fsck.txt
@@ -87,7 +87,7 @@ sorted properly etc), but on the whole if 'git-fsck' is happy, you
do have a valid tree.
Any corrupt objects you will have to find in backups or other archives
-(i.e., you can just remove them and do an `rsync` with some other site in
+(i.e., you can just remove them and do an 'rsync' with some other site in
the hopes that somebody else has the object you have corrupted).
Of course, "valid tree" doesn't mean that it wasn't generated by some