Documentation: quote {non-attributes} for asciidoc
Asciidoc treats {foo} as an attribute to be substituted; if 'foo' doesn't exist as an attribute, then the entire line gets dropped. When the literal {foo} is desired, \{foo} is required. The exceptions to this rule are: - inside literal blocks - if the 'foo' contains non-alphanumeric characters (e.g., {foo|bar} is assumed not to be an attribute) Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jeff King committed
Jul 2, 2007 at 01:24 UTC
967506bbbdc38e75263d6e6a90e3b8dbba6cec0f
4 files changed
+9
-9
Documentation/git-branch.txt
+1
-1
@@ -56,7 +56,7 @@ OPTIONS
56
-l::
57
Create the branch's ref log. This activates recording of
58
all changes to made the branch ref, enabling use of date
59
- based sha1 expressions such as "<branchname>@{yesterday}".
59
+ based sha1 expressions such as "<branchname>@\{yesterday}".
60
61
-f::
62
Force the creation of a new branch even if it means deleting
Documentation/git-checkout.txt
+1
-1
@@ -64,7 +64,7 @@ OPTIONS
64
-l::
65
Create the new branch's ref log. This activates recording of
66
all changes to made the branch ref, enabling use of date
67
- based sha1 expressions such as "<branchname>@{yesterday}".
67
+ based sha1 expressions such as "<branchname>@\{yesterday}".
68
69
-m::
70
If you have local modifications to one or more files that
Documentation/git-receive-pack.txt
+5
-5
@@ -48,8 +48,8 @@ standard input of the hook will be one line per ref to be updated:
48
The refname value is relative to $GIT_DIR; e.g. for the master
49
head this is "refs/heads/master". The two sha1 values before
50
each refname are the object names for the refname before and after
51
-the update. Refs to be created will have sha1-old equal to 0{40},
52
-while refs to be deleted will have sha1-new equal to 0{40}, otherwise
51
+the update. Refs to be created will have sha1-old equal to 0\{40},
52
+while refs to be deleted will have sha1-new equal to 0\{40}, otherwise
53
sha1-old and sha1-new should be valid objects in the repository.
54
55
This hook is called before any refname is updated and before any
@@ -71,7 +71,7 @@ The refname parameter is relative to $GIT_DIR; e.g. for the master
71
head this is "refs/heads/master". The two sha1 arguments are
72
the object names for the refname before and after the update.
73
Note that the hook is called before the refname is updated,
74
-so either sha1-old is 0{40} (meaning there is no such ref yet),
74
+so either sha1-old is 0\{40} (meaning there is no such ref yet),
75
or it should match what is recorded in refname.
76
77
The hook should exit with non-zero status if it wants to disallow
@@ -96,8 +96,8 @@ The refname value is relative to $GIT_DIR; e.g. for the master
96
head this is "refs/heads/master". The two sha1 values before
97
each refname are the object names for the refname before and after
98
the update. Refs that were created will have sha1-old equal to
99
-0{40}, while refs that were deleted will have sha1-new equal to
100
-0{40}, otherwise sha1-old and sha1-new should be valid objects in
99
+0\{40}, while refs that were deleted will have sha1-new equal to
100
+0\{40}, otherwise sha1-old and sha1-new should be valid objects in
101
the repository.
102
103
Using this hook, it is easy to generate mails describing the updates
Documentation/git-rev-list.txt
+2
-2
@@ -284,9 +284,9 @@ excluded from the output.
284
+
285
With '\--pretty' format other than oneline (for obvious reasons),
286
this causes the output to have two extra lines of information
287
-taken from the reflog. By default, 'commit@{Nth}' notation is
287
+taken from the reflog. By default, 'commit@\{Nth}' notation is
288
used in the output. When the starting commit is specified as
289
-'commit@{now}', output also uses 'commit@{timestamp}' notation
289
+'commit@{now}', output also uses 'commit@\{timestamp}' notation
290
instead. Under '\--pretty=oneline', the commit message is
291
prefixed with this information on the same line.
292