Re: How does GitGitGadget generate range-diffs, was Re: [PATCH v2 0/6] Support hashing objects larger than 4GB on Windows

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 17, 2026, 11:58 UTC
Message-ID: <xmqq4ij11ipp.fsf@gitster.g>
In-Reply-To: <fcb9e52a-5f71-1fd0-a18e-c48e22e6e28c@gmx.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> GitGitGadget is using range-diff to compare between iterations of
> essentially the same patches, therefore it encourages `range-diff` to try
> harder to look for matches via `--creation-factor=95`:

Thanks, I'll use the matching 95 in my local "sanity check after applying" step. As you say, it is not like comparing an integration branch with many topics with the same integration branch from a different day, which would need to avoid misidentifying two unrelted ones as if they are related, so the tool should asssume most of them match with each other.

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