From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Phillip Wood" <phillip.wood@dunelm.org.uk>,
"Patrick Steinhardt" <ps@pks.im>,
"Siddharth Asthana" <siddharthasthana31@gmail.com>
Cc: git@vger.kernel.org, "Christian Couder" <chriscool@tuxfamily.org>,
"Toon Claes" <toon@iotcl.com>,
"Karthik Nayak" <karthik.188@gmail.com>,
justin@parity.io
Subject: Re: [PATCH v1 1/1] rev-list: add --missing=print-only mode
Date: Mon, 20 Apr 2026 13:00:53 +0200 [thread overview]
Message-ID: <5bf346c1-0577-4b9b-8713-6053c97c6121@app.fastmail.com> (raw)
In-Reply-To: <491a27af-3ea4-4978-9d51-9c540ad31589@gmail.com>
On Mon, Apr 20, 2026, at 10:57, Phillip Wood wrote:
> On 20/04/2026 08:43, Patrick Steinhardt wrote:
>> On Sun, Apr 19, 2026 at 02:18:40PM +0530, Siddharth Asthana wrote:
>>
>>> static struct oidmap missing_objects;
>>> enum missing_action {
>>> - MA_ERROR = 0, /* fail if any missing objects are encountered */
>>> - MA_ALLOW_ANY, /* silently allow ALL missing objects */
>>> - MA_PRINT, /* print ALL missing objects in special section */
>>> - MA_PRINT_INFO, /* same as MA_PRINT but also prints missing object info */
>>> + MA_ERROR = 0, /* fail if any missing objects are encountered */
>>> + MA_ALLOW_ANY, /* silently allow ALL missing objects */
>>> + MA_PRINT, /* print ALL missing objects in special section */
>>> + MA_PRINT_INFO, /* same as MA_PRINT but also prints missing object info */
>>> + MA_PRINT_ONLY, /* print ONLY missing objects, without the "?" prefix */
>>
>> Makes me wonder whether we'll eventually also want to have
>> `MA_PRINT_INFO_ONLY`.
>
> Perhaps we'd be better to add a "--missing-only" option that limits the
> output to missing objects? That would avoid the problem of
> "--missing=print-only" not really explaining what it does as well.
The original `--missing` says what to do about missing objects. I find
`--missing=print-only` to be surprising:
• Do print missing
• But also do not print present objects
Why would a `--missing` option dictate what to do about objects that are
present (hide them)? That looks tacked-on.
`--missing-only` is better but has the same problem, IMO, of dictating
how present objects should be treated.
From the cover letter:
CV> At GitLab, Gitaly uses `rev-list --missing=print` to find missing
CV> objects in partial clones. The current output mixes present and missing
CV> objects together, with missing ones prefixed by '?', so Gitaly has to
CV> post-process the output to extract just the missing OIDs. Having a
CV> dedicated mode that outputs only the missing OIDs directly would
CV> simplify this.
This makes me think that I want:
1. I do want missing objects
2. I do not want present objects
Which makes me think that something like `--present=no-print` makes
more sense.
Just speaking as a user and not looking at the code.
>[snip]
next prev parent reply other threads:[~2026-04-20 11:01 UTC|newest]
Thread overview: 11+ 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 [this message]
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=5bf346c1-0577-4b9b-8713-6053c97c6121@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=justin@parity.io \
--cc=karthik.188@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
--cc=siddharthasthana31@gmail.com \
--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