diff options
Diffstat (limited to 'man1/git-interpret-trailers.1')
| -rw-r--r-- | man1/git-interpret-trailers.1 | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man1/git-interpret-trailers.1 b/man1/git-interpret-trailers.1 index 86eaa0f37..de5d34e57 100644 --- a/man1/git-interpret-trailers.1 +++ b/man1/git-interpret-trailers.1 @@ -2,12 +2,12 @@ .\" Title: git-interpret-trailers .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author] .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/> -.\" Date: 09/05/2022 +.\" Date: 09/09/2022 .\" Manual: Git Manual -.\" Source: Git 2.37.3.518.g79f2338b37 +.\" Source: Git 2.37.3.542.gdd3f6c4cae .\" Language: English .\" -.TH "GIT\-INTERPRET\-TRAI" "1" "09/05/2022" "Git 2\&.37\&.3\&.518\&.g79f233" "Git Manual" +.TH "GIT\-INTERPRET\-TRAI" "1" "09/09/2022" "Git 2\&.37\&.3\&.542\&.gdd3f6c" "Git Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -65,7 +65,7 @@ By default the new trailer will appear at the end of all the existing trailers\& .sp Existing trailers are extracted from the input message by looking for a group of one or more lines that (i) is all trailers, or (ii) contains at least one Git\-generated or user\-configured trailer and consists of at least 25% trailers\&. The group must be preceded by one or more empty (or whitespace\-only) lines\&. The group must either be at the end of the message or be the last non\-whitespace lines before a line that starts with \fI\-\-\-\fR (followed by a space or the end of the line)\&. Such three minus signs start the patch part of the message\&. See also \fB\-\-no\-divider\fR below\&. .sp -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\&. .sp Note that \fItrailers\fR do not follow and are not intended to follow many rules for RFC 822 headers\&. For example they do not follow the encoding rules and probably many other rules\&. .SH "OPTIONS" |