git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 5 in “What's cooking in git.git (Mar 2024, #08; Tue, 26)”
  1. Junio C HamanoMar 26, 2024
  2. Taylor BlauMar 26, 2024
  3. Junio C HamanoMar 26, 2024
  4. Taylor BlauMar 26, 2024
  5. Junio C HamanoMar 26, 2024

Read the whole thread, see it on lore, or plain text.

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