From: Rob Browning <rlb@defaultvalue.org>
To: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] signature-format.txt: explain and illustrate multi-line headers
Date: Thu, 14 Oct 2021 00:12:52 -0500 [thread overview]
Message-ID: <87zgrcgpez.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <xmqqtuhlisqe.fsf_-_@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> A signature attached to a signed commit, and the contents of the
> commit that merged a signed tag, are both recorded as a value of an
> object header field as a multi-line value, and are subject to the
> formatting convention for multi-line values in the headers, with a
> leading SP signaling that the rest of the line is a continuation of
> the previous line. Most notably, an empty line in such a multi-line
> value would result in a line with a sole SP on it.
One question I had was whether git's requirement was strictly a space,
or if it was following the rfc-822 convention where (if I remember
correctly) a tab is equivalent, i.e. the LWSP production in the grammar.
https://datatracker.ietf.org/doc/html/rfc822#section-3.2
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2021-10-14 5:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 16:33 [PATCH 1/1] signature-format.txt: add space to fix gpgsig continuation line Rob Browning
2021-10-11 16:41 ` 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 [this message]
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=87zgrcgpez.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).