From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Taylor Blau <ttaylorr@openai.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH 0/5] odb: make packfile generation pluggable
Date: Mon, 10 Aug 2026 07:25:46 +0200 [thread overview]
Message-ID: <anlg2rThlBLavyU8@pks.im> (raw)
In-Reply-To: <xmqq33wpej49.fsf@gitster.g>
On Fri, Aug 07, 2026 at 02:05:58PM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
>
> > Hi,
> >
> > this patch series makes packfile generation pluggable.
> >
> > Note that this series only makes those parts pluggable that are required
> > for the transport layer. The other parts that relate to packfile
> > generation as required by our repository maintenance is kept as-is, as
> > there is a bunch of options there that are way too specific to the
> > "files" backend to be portable. This should ultimately not be much of a
> > problem though, as maintenance itself is already pluggable in the first
> > place.
> >
> > It's a bit of a shame though for git-pack-objects(1), which still isn't
> > usable with alternate backends. I tried several times to find good
> > solutions for making it fully pluggable, but due to the backend-specific
> > options it's an utter mess. I want to eventually address this though:
> > same as with git-refs(1), I want to introduce git-objects(1) to care
> > about all things ODB. And as part of that command we can also introduce
> > a command that generates packfiles in a generic fashion, without all the
> > cruft that git-pack-objects(1) has. This is part of a future patch
> > series though.
> >
> > The series is built on top of 2c78326f81 (The 11th batch, 2026-08-05).
>
> With "--no-ref-delta" thing in flight, this will not play well with
> what is in 'seen', though.
Ah, dang, you're right. I'm not quite sure about the status of that
series -- there's been a discussion around whether it is the right fix
in the first case with Peff, and there wasn't an answer since Peff's
last mail.
Taylor, could you maybe share what your plans are? If you want to pursue
it further I'm happy to add it as a dependency and/or wait a bit.
Patrick
prev parent reply other threads:[~2026-08-10 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 10:45 [PATCH 0/5] odb: make packfile generation pluggable Patrick Steinhardt
2026-08-07 10:45 ` [PATCH 1/5] odb: introduce interface to generate packfiles Patrick Steinhardt
2026-08-07 10:45 ` [PATCH 2/5] upload-pack: generate packfiles via the object database Patrick Steinhardt
2026-08-07 10:45 ` [PATCH 3/5] send-pack: " Patrick Steinhardt
2026-08-07 10:45 ` [PATCH 4/5] builtin/bundle: refactor option handling for progress meter Patrick Steinhardt
2026-08-07 10:45 ` [PATCH 5/5] bundle: generate packfiles via the object database Patrick Steinhardt
2026-08-07 21:05 ` [PATCH 0/5] odb: make packfile generation pluggable Junio C Hamano
2026-08-10 5:25 ` Patrick Steinhardt [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=anlg2rThlBLavyU8@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=ttaylorr@openai.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