From: Rob Browning <rlb@defaultvalue.org>
To: git@vger.kernel.org
Subject: [PATCH 1/1] signature-format.txt: add space to fix gpgsig continuation line
Date: Sat, 9 Oct 2021 11:33:38 -0500 [thread overview]
Message-ID: <20211009163338.2175170-1-rlb@defaultvalue.org> (raw)
Add a space to the blank line after the version header in the example
gpgsig commit header.
Signed-off-by: Rob Browning <rlb@defaultvalue.org>
---
While investigating this (while parsing commit objects) I also
noticed a commit in a repo that had a blank continuation line (" \n")
after the "END PGP SIGNATURE" line.
Presuming that's valid, I suppose we could consider detailing any
additional specifications, i.e. what kind of trailing content a
parser should expect/ignore, etc.
Documentation/technical/signature-format.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/technical/signature-format.txt b/Documentation/technical/signature-format.txt
index 2c9406a56a..6acc0b1247 100644
--- a/Documentation/technical/signature-format.txt
+++ b/Documentation/technical/signature-format.txt
@@ -78,7 +78,7 @@ author A U Thor <author@example.com> 1465981137 +0000
committer C O Mitter <committer@example.com> 1465981137 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-
+
iQEcBAABAgAGBQJXYRjRAAoJEGEJLoW3InGJ3IwIAIY4SA6GxY3BjL60YyvsJPh/
HRCJwH+w7wt3Yc/9/bW2F+gF72kdHOOs2jfv+OZhq0q4OAN6fvVSczISY/82LpS7
DVdMQj2/YcHDT4xrDNBnXnviDO9G7am/9OE77kEbXrp7QPxvhjkicHNwy2rEflAA
--
2.30.2
next reply other threads:[~2021-10-09 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 16:33 Rob Browning [this message]
2021-10-11 16:41 ` [PATCH 1/1] signature-format.txt: add space to fix gpgsig continuation line Jeff King
2021-10-11 20:04 ` Junio C Hamano
2021-10-12 2:08 ` Jeff King
2021-10-12 16:54 ` Junio C Hamano
2021-10-13 2:06 ` [PATCH] signature-format.txt: explain and illustrate multi-line headers Junio C Hamano
2021-10-14 5:12 ` Rob Browning
2021-10-14 17:17 ` Junio C Hamano
2021-10-15 1:27 ` Rob Browning
2021-10-15 15:58 ` Junio C Hamano
2021-10-15 23:29 ` Rob Browning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211009163338.2175170-1-rlb@defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).