From: Junio C Hamano <gitster@pobox•com>
To: Taylor Blau <me@ttaylorr•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 14:02:41 -0700 [thread overview]
Message-ID: <xmqqo7b0905q.fsf@gitster.g> (raw)
In-Reply-To: <ZgM2zMykhkIAaXro@nand.local> (Taylor Blau's message of "Tue, 26 Mar 2024 16:57:48 -0400")
Taylor Blau <me@ttaylorr•com> writes:
> Sure, try this:
>
> The pack-bitmap machinery learned to write pseudo-merge bitmaps,
> which act as imaginary octopus merges covering un-bitmapped
> reference tips. This enhances bitmap coverage, and thus,
> performance, for repositories with many references using bitmaps.
Beautiful.
prev parent reply other threads:[~2024-03-26 21:02 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
2024-03-26 20:45 ` Junio C Hamano
2024-03-26 20:57 ` Taylor Blau
2024-03-26 21:02 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo7b0905q.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=me@ttaylorr$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox