From: Siddharth Asthana <siddharthasthana31@gmail.com>
To: Siddharth Shrimali <r.siddharth.shrimali@gmail.com>, git@vger.kernel.org
Cc: gitster@pobox.com, christian.couder@gmail.com, me@ttaylorr.com,
ps@pks.im, johannes.schindelin@gmx.de, l.s.r@web.de
Subject: Re: [RFC PATCH 0/7] repack: add --drop-filtered to reclaim space in partial clones
Date: Fri, 24 Jul 2026 00:56:02 +0530 [thread overview]
Message-ID: <f9c26c07-1dde-4bb6-a919-37d5229642f5@gmail.com> (raw)
In-Reply-To: <20260716132848.95982-1-r.siddharth.shrimali@gmail.com>
On 16/07/26 18:58, Siddharth Shrimali wrote:
> This is an RFC series seeking feedback on the design and approach.
> Several pieces are still missing (noted below) and the commit
> organization needs cleanup.
>
> Partial clones let you work with large repositories without downloading
> every blob up front and the missing blobs are lazily fetched from the promisor
> remote on demand. Over time, though, these lazily-fetched blobs
> accumulate locally and there is currently no safe, built-in way to
> reclaim that disk space instead of re-cloning.
>
> This series adds a "git repack --drop-filtered --filter=<spec>" command
> that removes large, locally-held promisor blobs that are recoverable
> from the promisor remote. The dropped blobs become absent locally but
> remain lazily re-fetchable, making the partial-clone still reversible.
>
> How it works:
> * Enumerate promisor objects directly (ODB_FOR_EACH_OBJECT_PROMISOR_ONLY)
> and select the blobs exceeding the filter threshold. Because every
> enumerated object is a promisor object, it is guaranteed recoverable and
> locally-created objects are never candidates.
This looks like the right approach to me. Going through the promisor
repack path instead of write_filtered_pack() matches how repack already
splits promisor objects out.
>
> * Rebuild the promisor pack without the selected blobs, reusing the
> existing repack machinery, so the drop is crash-safe.
>
> * Record each dropped object in a drop log
> ($GIT_DIR/objects/info/promisor-dropped) so a later change can
> explain a failed lazy fetch (when it was dropped, which filter
> matched, which remotes) instead of a bare "could not fetch" error.
>
> * --dry-run lists the candidates and changes nothing.
>
> Planned follow-ups:
> * Safety guards: refuse to run while a merge/rebase/cherry-pick is in
> progress, and refuse to drop blobs referenced by the current index.
I think these matter before we present this as a real space-reclaim
tool. Without the index guard especially, users may drop blobs and then
immediately fetch them back on the next command that needs the worktree.
The drop log and remote-object-info can wait. I would not block the
next RFC round on them.
On the UI, I am fine with a separate --dry-run for now (same as
Christian). We can revisit a --drop-filtered=<mode> form later if we
grow more drop-specific options.
Thanks.
Siddharth
>
> * Authoritative remote verification: the drop log currently lists all
> configured promisor remotes rather than the exact remote each object
> is recoverable from, because there is no client-side way to query a
> remote for object availability yet. A "remote-object-info" command
> is being added to the "git cat-file --batch" protocol for this. Once
> available, the exact remote can be recorded.
>
> Known issues to address in v2:
> * There is churn between "enumerate promisor blobs" and "actually drop
> filtered promisor blobs". The former introduces
> enumerate_promisor_blobs() with an interim signature that the latter
> rewrites. These will be reorganized so the function is introduced
> in its final form.
>
> * The tests are in a standalone commit. They will instead be
> distributed into the commits that introduce the behavior they test.
>
> Siddharth Shrimali (7):
> builtin/repack.c: add --drop-filtered and --dry-run options
> list-objects-filter: add list_objects_filter__filter_oidset()
> repack-promisor: allow excluding objects from the rebuilt promisor
> pack
> builtin/repack: enumerate promisor blobs for --drop-filtered
> t7706: test --drop-filtered enumeration and validation
> builtin/repack: actually drop filtered promisor blobs
> repack-promisor: record dropped objects in a drop log
>
> builtin/repack.c | 76 ++++++++++++++++-
> list-objects-filter.c | 45 ++++++++++
> list-objects-filter.h | 16 ++++
> repack-filtered.c | 81 ++++++++++++++++++
> repack-promisor.c | 106 ++++++++++++++++++++++-
> repack.h | 12 ++-
> t/meson.build | 1 +
> t/t7706-repack-drop-filtered.sh | 145 ++++++++++++++++++++++++++++++++
> 8 files changed, 478 insertions(+), 4 deletions(-)
> create mode 100755 t/t7706-repack-drop-filtered.sh
>
prev parent reply other threads:[~2026-07-23 19:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 13:28 [RFC PATCH 0/7] repack: add --drop-filtered to reclaim space in partial clones Siddharth Shrimali
2026-07-16 13:28 ` [RFC PATCH 1/7] builtin/repack.c: add --drop-filtered and --dry-run options Siddharth Shrimali
2026-07-16 21:08 ` Junio C Hamano
2026-07-17 18:00 ` Siddharth Shrimali
2026-07-23 19:31 ` Siddharth Asthana
2026-07-18 12:30 ` Christian Couder
2026-07-20 10:19 ` Siddharth Shrimali
2026-07-16 13:28 ` [RFC PATCH 2/7] list-objects-filter: add list_objects_filter__filter_oidset() Siddharth Shrimali
2026-07-16 13:28 ` [RFC PATCH 3/7] repack-promisor: allow excluding objects from the rebuilt promisor pack Siddharth Shrimali
2026-07-16 13:28 ` [RFC PATCH 4/7] builtin/repack: enumerate promisor blobs for --drop-filtered Siddharth Shrimali
2026-07-16 13:28 ` [RFC PATCH 5/7] t7706: test --drop-filtered enumeration and validation Siddharth Shrimali
2026-07-16 13:28 ` [RFC PATCH 6/7] builtin/repack: actually drop filtered promisor blobs Siddharth Shrimali
2026-07-23 19:42 ` Siddharth Asthana
2026-07-16 13:28 ` [RFC PATCH 7/7] repack-promisor: record dropped objects in a drop log Siddharth Shrimali
2026-07-23 19:41 ` Siddharth Asthana
2026-07-23 19:26 ` Siddharth Asthana [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=f9c26c07-1dde-4bb6-a919-37d5229642f5@gmail.com \
--to=siddharthasthana31@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=l.s.r@web.de \
--cc=me@ttaylorr.com \
--cc=ps@pks.im \
--cc=r.siddharth.shrimali@gmail.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