git-rm.txt: Fix quoting
Literal " produces typographically incorrect quotations, but "works" in most circumstances. In the subheadings of git-rm.txt, it "works" for the html backend but not for the docbook conversion to nroff: double "" and spurious double spaces appear in the output. Replace "incorrect" quotations by ``correct'' ones, and fix other "quotations" which are really `code fragments`. This should make git-rm.txt "-clean. Reported-by: Jeff King <peff@peff.net> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> Helped-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Michael J Gruber committed
Dec 7, 2010 at 10:07 UTC
f34e9edc7bbb41c52ff6a17dbffbef3d4979ee25
1 file changed
+6
-6
Documentation/git-rm.txt
+6
-6
@@ -89,8 +89,8 @@ the paths that have disappeared from the filesystem. However,
89
depending on the use case, there are several ways that can be
90
done.
91
92
-Using "git commit -a"
93
-~~~~~~~~~~~~~~~~~~~~~
92
+Using ``git commit -a''
93
+~~~~~~~~~~~~~~~~~~~~~~~
94
If you intend that your next commit should record all modifications
95
of tracked files in the working tree and record all removals of
96
files that have been removed from the working tree with `rm`
@@ -98,8 +98,8 @@ files that have been removed from the working tree with `rm`
98
automatically notice and record all removals. You can also have a
99
similar effect without committing by using `git add -u`.
100
101
-Using "git add -A"
102
-~~~~~~~~~~~~~~~~~~
101
+Using ``git add -A''
102
+~~~~~~~~~~~~~~~~~~~~
103
When accepting a new code drop for a vendor branch, you probably
104
want to record both the removal of paths and additions of new paths
105
as well as modifications of existing paths.
@@ -111,8 +111,8 @@ tree using this command:
111
git ls-files -z | xargs -0 rm -f
112
----------------
113
114
-and then "untar" the new code in the working tree. Alternately
115
-you could "rsync" the changes into the working tree.
114
+and then untar the new code in the working tree. Alternately
115
+you could 'rsync' the changes into the working tree.
116
117
After that, the easiest way to record all removals, additions, and
118
modifications in the working tree is: