git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2025, #03; Wed, 12)
Date: Mon, 17 Mar 2025 18:39:44 -0400	[thread overview]
Message-ID: <Z9iksBa4g2bUkX1u@nand.local> (raw)
In-Reply-To: <xmqqh63xx23f.fsf@gitster.g>

On Wed, Mar 12, 2025 at 04:26:28PM -0700, Junio C Hamano wrote:
> * tb/multi-cruft-pack-refresh-fix (2025-03-11) 6 commits
>  - builtin/pack-objects.c: freshen objects from existing cruft packs
>  - builtin/repack.c: simplify cruft pack aggregation
>  - pack-objects: generate cruft packs at most one object over threshold
>  - t/lib-cruft.sh: extract some cruft-related helpers
>  - t7704-repack-cruft.sh: consolidate `write_blob()`
>  - t/t5329-pack-objects-cruft.sh: evict 'repack'-related tests
>
>  Certain "cruft" objects would have never been refreshed when there
>  are multiple cruft packs in the repository, which has been
>  corrected.
>  source: <cover.1741648467.git.me@ttaylorr.com>

This one can be replaced with "v5" of this topic, which only fixes the
freshening bug, and punts on the --max-pack-size versus
--combine-cruft-below-size debacle.

I'll send a separate series to address the latter shortly.

> * tb/incremental-midx-part-2 (2024-11-20) 15 commits
>  - midx: implement writing incremental MIDX bitmaps
>  - pack-bitmap.c: use `ewah_or_iterator` for type bitmap iterators
>  - pack-bitmap.c: keep track of each layer's type bitmaps
>  - ewah: implement `struct ewah_or_iterator`
>  - pack-bitmap.c: apply pseudo-merge commits with incremental MIDXs
>  - pack-bitmap.c: compute disk-usage with incremental MIDXs
>  - pack-bitmap.c: teach `rev-list --test-bitmap` about incremental MIDXs
>  - pack-bitmap.c: support bitmap pack-reuse with incremental MIDXs
>  - pack-bitmap.c: teach `show_objects_for_type()` about incremental MIDXs
>  - pack-bitmap.c: teach `bitmap_for_commit()` about incremental MIDXs
>  - pack-bitmap.c: open and store incremental bitmap layers
>  - pack-revindex: prepare for incremental MIDX bitmaps
>  - Documentation: describe incremental MIDX bitmaps
>  - Merge branch 'tb/pseudo-merge-bitmap-fixes' into tb/incremental-midx-part-2
>  - Merge branch 'tb/incremental-midx-part-1' into tb/incremental-midx-part-2
>
>  Incrementally updating multi-pack index files.
>
>  Expecting a (hopefully minor and final) reroll.
>  cf. <Z8JSreTnEFlocYQ9@nand.local> <Z8JLbxBQh7XUpplz@nand.local>
>  source: <cover.1732054032.git.me@ttaylorr.com>

Thanks. This is rerolled, but it would be good to get some review from
others that are familiar with bitmaps before merging. It's not a very
long series by lines of code, but it is rather subtle, so the more
careful reviews it gets the better.

Thanks,
Taylor

  parent reply	other threads:[~2025-03-17 22:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 23:26 What's cooking in git.git (Mar 2025, #03; Wed, 12) Junio C Hamano
2025-03-13  0:08 ` en/merge-ort-prepare-to-remove-recursive (Was: Re: What's cooking in git.git (Mar 2025, #03; Wed, 12)) Elijah Newren
2025-03-13 23:35 ` What's cooking in git.git (Mar 2025, #03; Wed, 12) Usman Akinyemi
2025-03-17 22:39 ` Taylor Blau [this message]
2025-03-18 10:13 ` Karthik Nayak
2025-03-18 17:17   ` 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

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

  git send-email \
    --in-reply-to=Z9iksBa4g2bUkX1u@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.
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 NNTP newsgroup(s).