Re: [RFC PATCH 0/4] sign a SHA-256 digest of the tree in commits and tags

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 6, 2026, 22:38 UTC
Message-ID: <xmqqzewqbgk2.fsf@gitster.g>
In-Reply-To: <asVuadq79SNc-1y1@fruit.crustytoothpaste.net>

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

Show 6 quoted lines

> The reason more of the interoperability work has not gone upstream is
> because the pluggable ODB work has really ended up breaking a lot of
> things[0], so sending almost anything requires a bunch of rebasing and
> fixing, and I'm presently very burnt out, so I'm doing very little
> coding in my free time and doing more cycling, reading, and Factorio:
> Space Age.

If your time were corporate-funded, and if I declared that we would accept no changes other than the SHA-256 interoperability work and perhaps other low-impact changes, and that we would give anyone helping with the SHA-256 interoperability work the power to veto any topics that may interfere with quick integration of their work for N months, would it have worked better, I wonder?

Such an arrangement certainly requires buy-in from other stakeholders. Employers who fund scalability work would not only have to wait their turn, but might also need to be convinced to divert their resources to help this effort, so that the magic number N becomes smaller and they get their turn sooner, for example.