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

Johannes Schindelin [off-list ref] 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.