From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Dave Huseby <dwh@linuxprogrammer.org>, git@vger.kernel.org
Subject: Re: [RFC PATCH v1 1/1] Modifies documentation for universal cryptographic signing
Date: Sat, 8 May 2021 14:52:27 +0700 [thread overview]
Message-ID: <94624d84-be7e-016b-50f2-90a4c423be42@gmail.com> (raw)
In-Reply-To: <c454bcc4c3c5de1a17c63461c6091689098c75b9.1620454449.git.dwh@linuxprogrammer.org>
On 08/05/21 13.18, Dave Huseby wrote:
> +In mergtags, the whole signed tag object is stored in the field name
Oops, s/mergtags/mergetags/
> +The `sign` field is very similar to the old `gpgsig` field in commits. The data
> +is can be multi-line with subsequent lines starting with spaces to mark them as
> +additional data. The only difference is that the `sign` field stores signatures
> +with newlines and carriage returns escaped because whitespace is significate in
Oops, s/significate/significant/
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-05-08 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 6:18 [RFC PATCH v1 0/1] Universal cryptographic signing Dave Huseby
2021-05-08 6:18 ` [RFC PATCH v1 1/1] Modifies documentation for universal " Dave Huseby
2021-05-08 7:52 ` Bagas Sanjaya [this message]
2021-05-09 0:16 ` brian m. carlson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94624d84-be7e-016b-50f2-90a4c423be42@gmail.com \
--to=bagasdotme@gmail.com \
--cc=dwh@linuxprogrammer.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.
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 NNTP newsgroup(s).