Re: Semantics of change IDs (Re: Gerrit, GitButler, and Jujutsu projects collaborating on change-id commit footer)

From: Nico Williams <nico@cryptonector.com>
Date: Apr 23, 2025, 04:47 UTC
Message-ID: <aAhwzs62VPZrWr7+@ubby>
In-Reply-To: <aAg8HN6sgFu4mj1/@ubby>

On Tue, Apr 22, 2025 at 08:02:20PM -0500, Nico Williams wrote:

Show 6 quoted lines

> But remember that proponents want change IDs to not quite be unique,
> since the point is that they tie multiple different versions of a commit
> series together for the purpose of code review.  In the end, when the
> code review is completed and approved then the change ID might be unique
> again, but then cherry-picking onto other branches for forward- or
> back-porting might render them non-unique again.

Ah, right, the thing about change IDs getting copied to new commits when cherry-picking was my suggestion. I stand by it, but it's not what others are proposing.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.