@matheusbsbs / matheus-bagliano / commits / 438ded457b
Fork 0

Documentation: quoting trouble in "git rm" discussion

The current output (with Asciidoc 8.5.2) seems a bit broken: given two directories ‘d` and d2, there is a difference between using git rm 'd*’ and ‘git rm 'd/\*\’`, as the former will also remove all of directory d2. In other words, the markup parses as given two directories << d` and _d2_, there is a difference between using _git rm 'd* >>_ and << git rm 'd/\*\ >> `. I suspect there is an asciidoc bug involved (why is ' a candidate closing-quote mark when it is preceded by a backslash?) but with all the meanings of ` and ' involved I do not want to track it down. Better to use unambiguous {asterisk} and {apostrophe} entities. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Jonathan Nieder committed Aug 20, 2010 at 05:21 UTC 438ded457b6e0d1e615edd593faeeafdc8818fea
2 files changed +3 -1
Documentation/asciidoc.conf
+1
@@ -17,6 +17,7 @@ caret=&#94;
17 startsb=&#91;
18 endsb=&#93;
19 tilde=&#126;
20 +apostrophe=&#39;
21 backtick=&#96;
22
23 ifdef::backend-docbook[]
Documentation/git-rm.txt
+2 -1
@@ -78,7 +78,8 @@ a file that you have not told git about does not remove that file.
78
79 File globbing matches across directory boundaries. Thus, given
80 two directories `d` and `d2`, there is a difference between
81 -using `git rm \'d\*\'` and `git rm \'d/\*\'`, as the former will
81 +using `git rm {apostrophe}d{asterisk}{apostrophe}` and
82 +`git rm {apostrophe}d/{asterisk}{apostrophe}`, as the former will
83 also remove all of directory `d2`.
84
85 REMOVING FILES THAT HAVE DISAPPEARED FROM THE FILESYSTEM