| Message ID | ab11527ca58a7c3f0da657393088919acba78b00.1683566870.git.gitgitgadget@gmail.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | docs: interpret-trailers: reword and add examples | expand |
"Linus Arver via GitGitGadget" <gitgitgadget@gmail.com> writes: > From: Linus Arver <linusa@google.com> > > We already use angle brackets elsewhere, so this makes things more > consistent. Excellent. > > Signed-off-by: Linus Arver <linusa@google.com> > --- > Documentation/git-interpret-trailers.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/Documentation/git-interpret-trailers.txt b/Documentation/git-interpret-trailers.txt > index c4675d9d3bb..ac448fd732e 100644 > --- a/Documentation/git-interpret-trailers.txt > +++ b/Documentation/git-interpret-trailers.txt > @@ -62,9 +62,9 @@ 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 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 > +<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.
diff --git a/Documentation/git-interpret-trailers.txt b/Documentation/git-interpret-trailers.txt index c4675d9d3bb..ac448fd732e 100644 --- a/Documentation/git-interpret-trailers.txt +++ b/Documentation/git-interpret-trailers.txt @@ -62,9 +62,9 @@ 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 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 +<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.