Git development
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
	 Christian Couder <christian.couder@gmail.com>,
	Scott Chacon <scott@gitbutler.net>,
	git@vger.kernel.org,  Patrick Steinhardt <ps@pks.im>
Subject: Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags
Date: Wed, 7 Oct 2026 14:26:39 +0200	[thread overview]
Message-ID: <CAP8UFD3dnx3u6LL78pPSzreaTsSmoiJvofoR_R0Pyk7H6-8NXw@mail.gmail.com> (raw)
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:

> > 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.

[...]

> > 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.

  reply	other threads:[~2026-10-07 12:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  8:18 [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags Scott Chacon
2026-10-02  8:18 ` [RFC PATCH 1/4] tree-sha256: hash the contents of a tree with SHA-256 Scott Chacon
2026-10-02 15:45   ` Junio C Hamano
2026-10-02  8:18 ` [RFC PATCH 2/4] tag: add --hash=sha256 to sign a tree-sha256 header Scott Chacon
2026-10-02 15:49   ` Junio C Hamano
2026-10-02  8:18 ` [RFC PATCH 3/4] commit: " Scott Chacon
2026-10-02  8:18 ` [RFC PATCH 4/4] gpg: add gpg.treeHash to sign a tree-sha256 header by default Scott Chacon
2026-10-02 15:52 ` [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags Junio C Hamano
2026-10-02 19:06 ` brian m. carlson
2026-10-05  9:32   ` Scott Chacon
2026-10-05 12:41     ` Patrick Steinhardt
2026-10-05 14:16       ` Scott Chacon
2026-10-05 22:57         ` brian m. carlson
2026-10-06 13:36         ` Johannes Schindelin
2026-10-06 16:16       ` Kristoffer Haugsbakk
2026-10-06 21:55         ` brian m. carlson
2026-10-06 22:38           ` Junio C Hamano
2026-10-06 23:40             ` brian m. carlson
2026-10-06  9:00   ` Christian Couder
2026-10-06 22:26     ` brian m. carlson
2026-10-07 12:26       ` Christian Couder [this message]
2026-10-07 21:07         ` 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=CAP8UFD3dnx3u6LL78pPSzreaTsSmoiJvofoR_R0Pyk7H6-8NXw@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    --cc=sandals@crustytoothpaste.net \
    --cc=scott@gitbutler.net \
    /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