Re: What's cooking in git.git (Mar 2024, #08; Tue, 26)
- From
Taylor Blau <me@ttaylorr.com>
- Date
- Mar 26, 2024, 20:30 UTC
- Message-ID
- <ZgMwaG28aoC7Njcg@nand.local>
- In-Reply-To
- <xmqqle64algt.fsf@gitster.g>
On Tue, Mar 26, 2024 at 11:37:06AM -0700, Junio C Hamano wrote:
Show 8 quoted lines
> * tb/pseudo-merge-reachability-bitmap (2024-03-20) 24 commits > > [...] > > The pack-bitmap machinery has been extended to write bitmaps for > pseudo-merges, which are imaginary commits which act as octopus > merges covering groups of the un-bitmapped parts of history at > reference tips. This is good for ... what ...?
Instead of "this is good for ... what ...", let me know what you think of:
This allows for greater bitmap coverage (and, thus, performance when using bitmaps) of repositories with many references which ordinarily would not receive full coverage.
> Expecting a reroll.
I'm planning on sending one soon, but was hoping that Peff or someone else familiar with the bitmap machinery would look over some of the technical details first.
> cf. <ZfyxCLpjbaScIdWA@nand.local> > source: <cover.1710972293.git.me@ttaylorr.com>
Thanks, Taylor