git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2024, #08; Tue, 26)
Date: Tue, 26 Mar 2024 16:30:32 -0400	[thread overview]
Message-ID: <ZgMwaG28aoC7Njcg@nand.local> (raw)
In-Reply-To: <xmqqle64algt.fsf@gitster.g>

On Tue, Mar 26, 2024 at 11:37:06AM -0700, Junio C Hamano wrote:
> * 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


  reply	other threads:[~2024-03-26 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26 18:37 What's cooking in git.git (Mar 2024, #08; Tue, 26) Junio C Hamano
2024-03-26 20:30 ` Taylor Blau [this message]
2024-03-26 20:45   ` Junio C Hamano
2024-03-26 20:57     ` Taylor Blau
2024-03-26 21:02       ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZgMwaG28aoC7Njcg@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).