Re: git-send-email with GPG signed commits?
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Oct 20, 2022, 21:22 UTC
- Message-ID
- <Y1G8FKzHF4GJCaan@tapette.crustytoothpaste.net>
- In-Reply-To
- <4eb8707f-4686-e304-2aab-a6afee11abc9@cepl.eu>
On 2022-10-20 at 04:26:49, Matěj Cepl wrote:
Show 8 quoted lines
> Hello, > > did anybody even think about %subj%? Is there some effort somewhere making > git-send-email(1) supporting transfer of signed commits, where I could join? > I like hosting sites like sr.ht, which support git-send-email(1), but > unfortunately using that clears my submission off its GPG signatures. I > guess, it would be necessary to make some modifications to git-send-email(1) > and git-am(1). Is there some effort somewhere in that direction?
There's been discussion about this in the past on the list. I am personally in favour of a solution which allows us to preserve the committer and signature information in headers in the patch and apply that to synthesize a complete commit.
I know many people who work on a patch-based workflow _don't_ want to resynthesize the entire commit and would prefer to keep the current approach, which I also think is fine. However, there are situations where end-to-end provenance is useful and so is email, and I think it's worth supporting.
It is on my ever growing backlog of projects I'd like to implement but I don't have any immediate plans to do so.
-- brian m. carlson (he/him or they/them) Toronto, Ontario, CA