summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2022-09-09 12:02:25 -0700
committerJunio C Hamano <gitster@pobox.com>2022-09-09 12:02:25 -0700
commit00b0199c51fb6168cb219d9d4dc51d3692f72da9 (patch)
tree5430b81c1985ecd222b2932baf5b0578db204362
parent0e2a4764edea38c4aad95af246d6a7648a7d5e2d (diff)
parentb46dd1726c139c930d7b4b7c3262e3f2699987d3 (diff)
downloadgit-00b0199c51fb6168cb219d9d4dc51d3692f72da9.tar.xz
Merge branch 'cc/doc-trailer-whitespace-rules'
Doc update. * cc/doc-trailer-whitespace-rules: Documentation: clarify whitespace rules for trailers
-rw-r--r--Documentation/git-interpret-trailers.txt10
1 files changed, 6 insertions, 4 deletions
diff --git a/Documentation/git-interpret-trailers.txt b/Documentation/git-interpret-trailers.txt
index 956a01d184..6d6197cd0a 100644
--- a/Documentation/git-interpret-trailers.txt
+++ b/Documentation/git-interpret-trailers.txt
@@ -60,10 +60,12 @@ non-whitespace lines before a line that starts with '---' (followed by a
space or the end of the line). Such three minus signs start the patch
part of the message. See also `--no-divider` below.
-When reading trailers, there can be whitespaces after the
-token, the separator and the value. There can also be whitespaces
-inside the token and the value. The value may be split over multiple lines with
-each subsequent line starting with whitespace, like the "folding" in RFC 822.
+When reading trailers, there can be no whitespace before or inside the
+token, but any number of regular space and tab characters are allowed
+between the token and the separator. There can be whitespaces before,
+inside or after the value. The value may be split over multiple lines
+with each subsequent line starting with at least one whitespace, like
+the "folding" in RFC 822.
Note that 'trailers' do not follow and are not intended to follow many
rules for RFC 822 headers. For example they do not follow