From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/5] pack-objects: brown-paper-bag fixes for multi-pack reuse
Date: Tue, 27 Aug 2024 17:13:24 -0400 [thread overview]
Message-ID: <cover.1724793201.git.me@ttaylorr.com> (raw)
This series fixes a couple of issues (some cosmetic, others less so) in
multi-pack reuse noticed when rolling this out over a few real-world,
internal repositories on GitHub's servers.
The patches are laid out as follows:
- The first three patches demonstrate, prepare for, and fix a
significant bug with multi-pack reuse which results in all sorts of
strange behavior (explained in detail in the third commit of this
series).
- The fourth patch is a minor (mostly cosmetic) performance
optimization that avoids duplicate calls to pack_pos_to_offset()
when performing pack-reuse with a MIDX bitmap.
- The final patch is a cosmetic fix to avoid using the value of a
constant instead of the name constant itself.
Thanks in advance for your review!
Taylor Blau (5):
t/t5332-multi-pack-reuse.sh: verify pack generation with --strict
pack-bitmap: tag bitmapped packs with their corresponding MIDX
builtin/pack-objects.c: translate bit positions during pack-reuse
pack-bitmap.c: avoid repeated `pack_pos_to_offset()` during reuse
builtin/pack-objects.c: do not open-code `MAX_PACK_OBJECT_HEADER`
builtin/pack-objects.c | 46 +++++++++++++++++++++++++++++--------
midx.c | 1 +
pack-bitmap.c | 12 ++++++----
pack-bitmap.h | 1 +
t/t5332-multi-pack-reuse.sh | 35 ++++++++++++++++++++++++----
5 files changed, 78 insertions(+), 17 deletions(-)
base-commit: 159f2d50e75c17382c9f4eb7cbda671a6fa612d1
--
2.46.0.426.g82754d92509
next reply other threads:[~2024-08-27 21:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 21:13 Taylor Blau [this message]
2024-08-27 21:13 ` [PATCH 1/5] t/t5332-multi-pack-reuse.sh: verify pack generation with --strict Taylor Blau
2024-08-27 21:13 ` [PATCH 2/5] pack-bitmap: tag bitmapped packs with their corresponding MIDX Taylor Blau
2024-08-28 0:14 ` Junio C Hamano
2024-08-29 18:58 ` Taylor Blau
2024-09-05 9:00 ` Jeff King
2024-09-17 9:58 ` Taylor Blau
2024-08-27 21:13 ` [PATCH 3/5] builtin/pack-objects.c: translate bit positions during pack-reuse Taylor Blau
2024-09-04 18:18 ` Junio C Hamano
2024-08-27 21:13 ` [PATCH 4/5] pack-bitmap.c: avoid repeated `pack_pos_to_offset()` during reuse Taylor Blau
2024-09-04 18:54 ` Junio C Hamano
2024-09-04 19:28 ` Taylor Blau
2024-08-27 21:13 ` [PATCH 5/5] builtin/pack-objects.c: do not open-code `MAX_PACK_OBJECT_HEADER` Taylor Blau
2024-09-04 18:56 ` [PATCH 0/5] pack-objects: brown-paper-bag fixes for multi-pack reuse Junio C Hamano
2024-09-04 19:28 ` Taylor Blau
2024-09-05 9:10 ` Jeff King
2024-09-05 15:21 ` 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=cover.1724793201.git.me@ttaylorr.com \
--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.
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).