Documentation: remove unnecessary backslashes
asciidoctor does not remove backslashes used to escape curly brackets from the HTML output if the contents of the curly brackets are empty or contain at least a <, -, or space. asciidoc does not require the backslashes in these cases, so just remove them. Signed-off-by: Matthew Kraai <matt.kraai@abbott.com> Reported-by: Philip Oakley <philipoakley@iee.org> Reviewed-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Matthew Kraai committed
Jan 20, 2016 at 09:21 UTC
c200deb829ab6485e90d02c9c0e193d33cbaec4b
1 file changed
+10
-10
Documentation/revisions.txt
+10
-10
@@ -61,11 +61,11 @@ some output processing may assume ref names in UTF-8.
61
'@'::
62
'@' alone is a shortcut for 'HEAD'.
63
64
-'<refname>@\{<date>\}', e.g. 'master@\{yesterday\}', 'HEAD@\{5 minutes ago\}'::
64
+'<refname>@{<date>}', e.g. 'master@\{yesterday\}', 'HEAD@{5 minutes ago}'::
65
A ref followed by the suffix '@' with a date specification
66
enclosed in a brace
67
- pair (e.g. '\{yesterday\}', '\{1 month 2 weeks 3 days 1 hour 1
68
- second ago\}' or '\{1979-02-26 18:30:00\}') specifies the value
67
+ pair (e.g. '\{yesterday\}', '{1 month 2 weeks 3 days 1 hour 1
68
+ second ago}' or '{1979-02-26 18:30:00}') specifies the value
69
of the ref at a prior point in time. This suffix may only be
70
used immediately following a ref name and the ref must have an
71
existing log ('$GIT_DIR/logs/<ref>'). Note that this looks up the state
@@ -73,7 +73,7 @@ some output processing may assume ref names in UTF-8.
73
'master' branch last week. If you want to look at commits made during
74
certain times, see '--since' and '--until'.
75
76
-'<refname>@\{<n>\}', e.g. 'master@\{1\}'::
76
+'<refname>@{<n>}', e.g. 'master@\{1\}'::
77
A ref followed by the suffix '@' with an ordinal specification
78
enclosed in a brace pair (e.g. '\{1\}', '\{15\}') specifies
79
the n-th prior value of that ref. For example 'master@\{1\}'
@@ -82,13 +82,13 @@ some output processing may assume ref names in UTF-8.
82
immediately following a ref name and the ref must have an existing
83
log ('$GIT_DIR/logs/<refname>').
84
85
-'@\{<n>\}', e.g. '@\{1\}'::
85
+'@{<n>}', e.g. '@\{1\}'::
86
You can use the '@' construct with an empty ref part to get at a
87
reflog entry of the current branch. For example, if you are on
88
branch 'blabla' then '@\{1\}' means the same as 'blabla@\{1\}'.
89
90
-'@\{-<n>\}', e.g. '@\{-1\}'::
91
- The construct '@\{-<n>\}' means the <n>th branch/commit checked out
90
+'@{-<n>}', e.g. '@{-1}'::
91
+ The construct '@{-<n>}' means the <n>th branch/commit checked out
92
before the current one.
93
94
'<branchname>@\{upstream\}', e.g. 'master@\{upstream\}', '@\{u\}'::
@@ -139,7 +139,7 @@ from one location and push to another. In a non-triangular workflow,
139
'<rev>{caret}1{caret}1{caret}1'. See below for an illustration of
140
the usage of this form.
141
142
-'<rev>{caret}\{<type>\}', e.g. 'v0.99.8{caret}\{commit\}'::
142
+'<rev>{caret}{<type>}', e.g. 'v0.99.8{caret}\{commit\}'::
143
A suffix '{caret}' followed by an object type name enclosed in
144
brace pair means dereference the object at '<rev>' recursively until
145
an object of type '<type>' is found or the object cannot be
@@ -159,13 +159,13 @@ it does not have to be dereferenced even once to get to an object.
159
'rev{caret}\{tag\}' can be used to ensure that 'rev' identifies an
160
existing tag object.
161
162
-'<rev>{caret}\{\}', e.g. 'v0.99.8{caret}\{\}'::
162
+'<rev>{caret}{}', e.g. 'v0.99.8{caret}{}'::
163
A suffix '{caret}' followed by an empty brace pair
164
means the object could be a tag,
165
and dereference the tag recursively until a non-tag object is
166
found.
167
168
-'<rev>{caret}\{/<text>\}', e.g. 'HEAD^{/fix nasty bug}'::
168
+'<rev>{caret}{/<text>}', e.g. 'HEAD^{/fix nasty bug}'::
169
A suffix '{caret}' to a revision parameter, followed by a brace
170
pair that contains a text led by a slash,
171
is the same as the ':/fix nasty bug' syntax below except that