Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Oct 7, 2026, 12:26 UTC
- Message-ID
- <CAP8UFD3dnx3u6LL78pPSzreaTsSmoiJvofoR_R0Pyk7H6-8NXw@mail.gmail.com>
- In-Reply-To
- <asV1oB_avuEbgRVe@fruit.crustytoothpaste.net>
On Wed, Oct 7, 2026 at 12:26 AM brian m. carlson <sandals@crustytoothpaste.net> wrote:
> > On 2026-10-06 at 09:00:45, Christian Couder wrote:
Show 5 quoted lines
> > Is the current state of the work publicly available somewhere? Or > > could you make it publicly available somewhere? (Fine if it's only as > > patches in a tarball.) > > Yeah, it's at https://github.com/bk2204/git.git as `sha256-interop`.
Thanks.
[...]
Show 8 quoted lines
> > If some of us could help you, how could we best help? > > I would love someone to start picking up patches from the early part of > the series, rebasing them onto `master`, fixing up any conflicts, and > polishing them, and then sending them in. The `sha256-interop-part-2` > series would be great for that. > > Just let me know if you want to do this and then we won't conflict.
I am willing to help, but it's not likely I will have a lot of time to work on it before the end of next month. Anyway let me see if I can upstream some parts of the `sha256-interop-part-2` series this week or next week...
Thanks, Christian.