Re: Gerrit, GitButler, and Jujutsu projects collaborating on change-id commit footer

From: Nico Williams <nico@cryptonector.com>
Date: Apr 4, 2025, 16:04 UTC
Message-ID: <Z/ADDp/mIzuOofYl@ubby>
In-Reply-To: <Z--nnOhsUCaqo45z@pks.im>

On Fri, Apr 04, 2025 at 11:34:20AM +0200, Patrick Steinhardt wrote:

Show 6 quoted lines

> > Ah, well, Git does have an index: refs.  You could use
> > refs/change-IDs/<change-ID> to index by change ID.
> 
> I don't think references are a good mechanism to track change IDs. The
> expectation around refs is that users can change them basically at will,
> but it certainly does not make any sense to let them update change IDs.

git meta (a separate project) uses refs named refs/commits/$full_hash. Users can always break their repos in a many many ways. Using refs is fine.

> Furthermore, as we have already discussed, change IDs are not unique,
> but refs can only point to a single commit ID. So that's another
> mismatch that we cannot address.

Oh I agree with that!  But I think I've made that pretty clear by now :]

However one could have refs/change-IDs/<change-ID> ultimately point to an object that lists the commits with that change ID, and then that would function as an index for non-unique change IDs.

> I think caching the information in an auxiliary data structure would
> thus be a lot more reasonable. This could for example be part of commit
> graphs, but could also be a separate index specific to change IDs
> themselves.

Sure.