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

Re: git-send-email with GPG signed commits?

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 20, 2022, 17:48 UTC
Message-ID
<xmqqr0z2s7w4.fsf@gitster.g>
In-Reply-To
<Y1GJAart+/yFc5MR@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
> So commit signatures are generally an attestation by the committer, not
> by the author. It's just that the two are usually the same when you are
> committing locally.
>
> I think you would need some kind of "author-sig" header that signs the
> commit object bytes _without_ the commit header at all. And that assumes
> the maintainer's workflow is to never modify a patch in transit, and to
> apply it at the exact same spot that you wrote it (so that the parent
> and tree ids remain the same).

Doesn't it immediately break down once you send a 2-patch series? You may be able to get the bottom one right, but the top one needs to depend on the commit object name of the result of applying the bottom one.

It depends on what they are trying to achieve by transferrring with existing signature intact. If they truly want to preserve the validity of the signatures on commits, they are better off exchanging bundles over e-mail, as reviewers and integrators are not even allowed to touch anything.

Previous: Jeff KingNext: Junio C Hamano
Message 6 of 13 in “git-send-email with GPG signed commits?”
  1. Matěj CeplOct 20, 2022
  2. Konstantin RyabitsevOct 20, 2022
  3. Matěj CeplOct 20, 2022
  4. Konstantin RyabitsevOct 20, 2022
  5. Jeff KingOct 20, 2022
  6. Junio C HamanoOct 20, 2022
  7. Junio C HamanoOct 20, 2022
  8. Jeff KingOct 20, 2022
  9. Konstantin RyabitsevOct 20, 2022
  10. rsbecker@nexbridge.comOct 20, 2022
  11. Matěj CeplOct 20, 2022
  12. brian m. carlsonOct 20, 2022
  13. Matěj CeplOct 21, 2022

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.