doc: trailer: use angle brackets for <token> and <value>
We already use angle brackets elsewhere, so this makes things more consistent. Signed-off-by: Linus Arver <linusa@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Linus Arver committed
Jun 15, 2023 at 02:53 UTC
8e80f2916b82501b9d726b75ba0df32c951e4a7e
1 file changed
+4
-4
Documentation/git-interpret-trailers.txt
+4
-4
@@ -66,9 +66,9 @@ non-whitespace lines before a line that starts with '---' (followed by a
66
space or the end of the line).
67
68
When reading trailers, there can be no whitespace before or inside the
69
-token, but any number of regular space and tab characters are allowed
70
-between the token and the separator. There can be whitespaces before,
71
-inside or after the value. The value may be split over multiple lines
69
+<token>, but any number of regular space and tab characters are allowed
70
+between the <token> and the separator. There can be whitespaces before,
71
+inside or after the <value>. The <value> may be split over multiple lines
72
with each subsequent line starting with at least one whitespace, like
73
the "folding" in RFC 822.
74
@@ -241,7 +241,7 @@ trailer.<token>.command::
241
This option behaves in the same way as 'trailer.<token>.cmd', except
242
that it doesn't pass anything as argument to the specified command.
243
Instead the first occurrence of substring $ARG is replaced by the
244
- value that would be passed as argument.
244
+ <value> that would be passed as argument.
245
+
246
The 'trailer.<token>.command' option has been deprecated in favor of
247
'trailer.<token>.cmd' due to the fact that $ARG in the user's command is