git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH v1 1/1] Modifies documentation for universal cryptographic signing

From
Bagas Sanjaya <bagasdotme@gmail.com>
Date
May 8, 2021, 07:52 UTC
Message-ID
<94624d84-be7e-016b-50f2-90a4c423be42@gmail.com>
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
Previous: Dave HusebyNext: brian m. carlson
Message 3 of 4 in “Universal cryptographic signing”
  1. 0/1 Universal cryptographic signingDave Huseby, May 8, 2021
  2. 1/1 Modifies documentation for universal cryptographic signingDave Huseby, May 8, 2021
  3. Bagas SanjayaMay 8, 2021
  4. brian m. carlsonMay 9, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.