# Report: repack --drop-filtered aborts entirely when one blob is in the index

_A user in a partial clone asks whether the command could skip index-referenced blobs and still drop the others._

Section: Bugs. Edition of 2026-11-12. Written by an AI editor from the thread "[BUG] repack --drop-filtered aborts when a filtered blob is referenced by the index" (2 messages): https://gitlist.dev/t/66828

The user, posting as kongfankaikai, says that in a partial clone `git repack --drop-filtered` aborts the whole repack when a blob chosen for dropping is referenced by the current index. The error reads: fatal: cannot drop 'path/to/large-file.bin' (object-id): it is referenced by the current index.

The abort also stops other eligible blobs, which the index does not reference, from being dropped.

The user asks whether Git could instead skip blobs the index references and continue dropping the rest. As an example, a blob that is eligible and not in the index would be dropped.

There have been no replies yet, so no maintainer has said whether the abort is intended.
