From: Siddharth Asthana <siddharthasthana31@gmail.com>
To: git@vger.kernel.org
Cc: chriscool@tuxfamily.org, toon@iotcl.com, ps@pks.im,
karthik.188@gmail.com, justin@parity.io, peff@peff.net,
phillip.wood123@gmail.com,
Siddharth Asthana <siddharthasthana31@gmail.com>
Subject: [PATCH v3 0/1] rev-list: add --missing-only option to filter output
Date: Fri, 4 Sep 2026 02:15:50 +0530 [thread overview]
Message-ID: <20260903204551.65592-1-siddharthasthana31@gmail.com> (raw)
In-Reply-To: <20260901185100.33948-1-siddharthasthana31@gmail.com>
Hi,
v2 added --missing-only as a filter next to --missing=print /
--missing=print-info. Junio asked how the missing list is used, so
this v3 only updates the log message.
It is a one-shot walk. Gitaly uses --missing=print when packing a
quarantine and treats '?' lines as objects that must already be in
the main repo. Tests do the same (is this blob still missing).
--missing-only is that list without the prefix, not a fetch loop.
Based on 1630431f32 (The 21st batch, 2026-08-31).
Changes from v2:
- Stronger motivation in the commit message (Junio).
- Link to v2:
https://lore.kernel.org/git/20260901185100.33948-1-siddharthasthana31@gmail.com/
Thanks,
Siddharth
---
Siddharth Asthana (1):
rev-list: add --missing-only option to filter output
Documentation/rev-list-options.adoc | 13 ++++++++
builtin/rev-list.c | 42 ++++++++++++++++++++++---
t/t6022-rev-list-missing.sh | 49 +++++++++++++++++++++++++++++
3 files changed, 99 insertions(+), 5 deletions(-)
Range-diff versus v2:
1: 3c89e6bc38 ! 1: c751ff41a4 rev-list: add --missing-only option to filter output
@@ Commit message
git rev-list --objects --all --missing=print | perl -ne 'print if s/^[?]//'
+ This is for a one-shot walk, not a fetch loop. Callers already have
+ --missing=print and strip the leading '?'. Gitaly does that when packing
+ a quarantine: '?' lines are objects that must already exist in the main
+ repo. Tests do the same (is this blob still missing). --missing-only is
+ just that list without the prefix.
+
Add --missing-only. Use it with --missing=print or --missing=print-info
to print only missing objects. --missing= still picks the format;
--missing-only only filters. The leading '?' is omitted. With
base-commit: 1630431f326e15fcde608827b5ff38422528eb59
next prev parent reply other threads:[~2026-09-03 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 8:48 [PATCH v1 0/1] rev-list: add --missing=print-only mode Siddharth Asthana
2026-04-19 8:48 ` [PATCH v1 1/1] " Siddharth Asthana
2026-04-19 22:36 ` Derrick Stolee
2026-04-20 10:24 ` Siddharth Asthana
2026-04-20 11:44 ` Derrick Stolee
2026-04-20 7:43 ` Patrick Steinhardt
2026-04-20 8:57 ` Phillip Wood
2026-04-20 9:55 ` Patrick Steinhardt
2026-04-20 10:37 ` Siddharth Asthana
2026-04-20 11:00 ` Kristoffer Haugsbakk
2026-04-20 10:33 ` Siddharth Asthana
2026-09-01 18:50 ` [PATCH v2 0/1] rev-list: add --missing-only option to filter output Siddharth Asthana
2026-09-01 18:51 ` [PATCH v2 1/1] " Siddharth Asthana
2026-09-01 19:57 ` [PATCH v2 0/1] " Junio C Hamano
2026-09-01 20:27 ` Siddharth Asthana
2026-09-02 21:26 ` Junio C Hamano
2026-09-03 20:45 ` Siddharth Asthana [this message]
2026-09-03 20:45 ` [PATCH v3 1/1] " Siddharth Asthana
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=20260903204551.65592-1-siddharthasthana31@gmail.com \
--to=siddharthasthana31@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=justin@parity.io \
--cc=karthik.188@gmail.com \
--cc=peff@peff.net \
--cc=phillip.wood123@gmail.com \
--cc=ps@pks.im \
--cc=toon@iotcl.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