From: Patrick Steinhardt <ps@pks.im>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 6/6] packfile: rename `packfile_store_get_all_packs()`
Date: Thu, 9 Oct 2025 08:36:19 +0200 [thread overview]
Message-ID: <aOdX4_e9K_1p1pyv@pks.im> (raw)
In-Reply-To: <aObOFciwYsvTWT0e@nand.local>
On Wed, Oct 08, 2025 at 04:48:21PM -0400, Taylor Blau wrote:
> On Tue, Oct 07, 2025 at 02:41:12PM +0200, Patrick Steinhardt wrote:
> > ---
> > builtin/fast-import.c | 4 ++--
> > builtin/pack-objects.c | 4 ++--
> > packfile.c | 2 +-
> > packfile.h | 4 ++--
> > 4 files changed, 7 insertions(+), 7 deletions(-)
>
> Hmm. I wonder if we should perform this step at a later date. My fear is
> that another topic in fight might introduce a new use of the "get_packs"
> assuming the old semantics.
>
> Merging this topic and that hypothetical one together wouldn't produce a
> textual conflict, but it could introduce bugs where the hypothetical new
> code expects the old behavior.
>
> Perhaps I'm overthinking this, but figured I'd write down the concern
> nonetheless.
I think that in many cases, a callsite that doesn't handle MIDX'd packs
specifically with `get_packs()` is almost guaranteed to be wrong in some
cases anyway due to `get_packs()` and `get_all_packs()` influencing each
other's results. In this series we already saw that the callsites handle
this correctly even though they use `get_packs()`, and any new callsites
would probably have to do the same.
So I don't think this is too worrisome overall.
Patrick
next prev parent reply other threads:[~2025-10-09 6:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 12:41 [PATCH 0/6] packfile: remove `packfile_store_get_packs()` Patrick Steinhardt
2025-10-07 12:41 ` [PATCH 1/6] object-name: convert to use `packfile_store_get_all_packs()` Patrick Steinhardt
2025-10-08 20:21 ` Taylor Blau
2025-10-07 12:41 ` [PATCH 2/6] builtin/gc: " Patrick Steinhardt
2025-10-08 20:25 ` Taylor Blau
2025-10-09 6:36 ` Patrick Steinhardt
2025-10-07 12:41 ` [PATCH 3/6] builtin/grep: simplify how we preload packs Patrick Steinhardt
2025-10-08 20:43 ` Taylor Blau
2025-10-07 12:41 ` [PATCH 4/6] packfile: drop `packfile_store_get_packs()` Patrick Steinhardt
2025-10-08 20:44 ` Taylor Blau
2025-10-07 12:41 ` [PATCH 5/6] packfile: introduce macro to iterate through packs Patrick Steinhardt
2025-10-08 21:15 ` Taylor Blau
2025-10-09 6:36 ` Patrick Steinhardt
2025-10-07 12:41 ` [PATCH 6/6] packfile: rename `packfile_store_get_all_packs()` Patrick Steinhardt
2025-10-08 20:48 ` Taylor Blau
2025-10-09 6:36 ` Patrick Steinhardt [this message]
2025-10-09 8:01 ` [PATCH v2 0/6] packfile: remove `packfile_store_get_packs()` Patrick Steinhardt
2025-10-09 8:01 ` [PATCH v2 1/6] object-name: convert to use `packfile_store_get_all_packs()` Patrick Steinhardt
2025-10-14 19:07 ` Justin Tobler
2025-10-09 8:01 ` [PATCH v2 2/6] builtin/gc: " Patrick Steinhardt
2025-10-09 8:01 ` [PATCH v2 3/6] builtin/grep: simplify how we preload packs Patrick Steinhardt
2025-10-09 8:01 ` [PATCH v2 4/6] packfile: drop `packfile_store_get_packs()` Patrick Steinhardt
2025-10-14 19:11 ` Justin Tobler
2025-10-09 8:01 ` [PATCH v2 5/6] packfile: introduce macro to iterate through packs Patrick Steinhardt
2025-10-14 19:17 ` Justin Tobler
2025-10-09 8:01 ` [PATCH v2 6/6] packfile: rename `packfile_store_get_all_packs()` Patrick Steinhardt
2025-10-14 19:19 ` [PATCH v2 0/6] packfile: remove `packfile_store_get_packs()` Justin Tobler
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=aOdX4_e9K_1p1pyv@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.