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,
Siddharth Asthana <siddharthasthana31@gmail.com>
Subject: [PATCH v1 0/1] rev-list: add --missing=print-only mode
Date: Sun, 19 Apr 2026 14:18:39 +0530 [thread overview]
Message-ID: <20260419084840.33986-1-siddharthasthana31@gmail.com> (raw)
Hi,
At GitLab, Gitaly uses `rev-list --missing=print` to find missing
objects in partial clones. The current output mixes present and missing
objects together, with missing ones prefixed by '?', so Gitaly has to
post-process the output to extract just the missing OIDs. Having a
dedicated mode that outputs only the missing OIDs directly would
simplify this.
This patch adds --missing=print-only which suppresses all regular
object output and prints only the missing OIDs, one per line, without
the '?' prefix. A `missing_action_prints()` helper consolidates the
repeated three-way checks for MA_PRINT/MA_PRINT_INFO/MA_PRINT_ONLY.
The series is based on top of 9f223ef1c0 (Git 2.54-rc2).
CI: https://gitlab.com/gitlab-org/git/-/pipelines/2463294546
Siddharth Asthana (1):
rev-list: add --missing=print-only mode
Documentation/rev-list-options.adoc | 5 +++
builtin/rev-list.c | 49 ++++++++++++++++++++++-------
t/t6022-rev-list-missing.sh | 26 +++++++++++++++
3 files changed, 68 insertions(+), 12 deletions(-)
base-commit: 9f223ef1c026d91c7ac68cc0211bde255dda6199
Thanks
- Siddharth
next reply other threads:[~2026-04-19 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 8:48 Siddharth Asthana [this message]
2026-04-19 8:48 ` [PATCH v1 1/1] rev-list: add --missing=print-only mode 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
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=20260419084840.33986-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=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