Christian Couder <christian.couder@xxxxxxxxx> writes: > - rebased on top of 6c8e4ee870 (The sixteenth batch, 2022-08-29), > - added my "Signed-off-by: ...", > - clarified that there can be no whitespace before the token, > - clarified that "any number of regular space and tab characters are > allowed between the token and the separator". > > Documentation/git-interpret-trailers.txt | 10 ++++++---- > 1 file changed, 6 insertions(+), 4 deletions(-) Looks good. Thanks. Will queue. > > 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
