From: Pablo Sabater <pabloosabaterr@gmail.com>
To: git@vger.kernel.org
Cc: Derrick Stolee <stolee@gmail.com>,
Pablo Sabater <pabloosabaterr@gmail.com>
Subject: [PATCH RFC 1/5] transport-internal: update fetch_object_info comment
Date: Wed, 30 Sep 2026 01:21:46 +0100 [thread overview]
Message-ID: <20260930-backfill-dryrun-v1-1-1128f247ee01@gmail.com> (raw)
In-Reply-To: <20260930-backfill-dryrun-v1-0-1128f247ee01@gmail.com>
The comment describing the fetch_object_info() callback in struct
transport_vtable says that only the object size can be fetched. The
object-info capability can now also report the object type, or
neither, to only check whether an object exists on the remote.
Update the comment.
Signed-off-by: Pablo Sabater <pabloosabaterr@gmail.com>
---
transport-internal.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/transport-internal.h b/transport-internal.h
index a10b27cc81..626ceaae2b 100644
--- a/transport-internal.h
+++ b/transport-internal.h
@@ -48,8 +48,8 @@ struct transport_vtable {
int (*fetch_refs)(struct transport *transport, int refs_nr, struct ref **refs);
/*
- * Fetch object info (only size currently) from remote without
- * downloading the objects.
+ * Fetch object info (size, type, or none of them to only check
+ * for existence) from the remote without downloading the objects.
*
* Uses object-info capability of v2 protocol.
*/
--
2.54.0
next prev parent reply other threads:[~2026-09-30 0:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 0:21 [PATCH RFC 0/5] Add --dry-run option to git-backfill(1) Pablo Sabater
2026-09-30 0:21 ` Pablo Sabater [this message]
2026-09-30 0:21 ` [PATCH RFC 2/5] fetch-object-info: add enum for fetch_object_info() statuses Pablo Sabater
2026-09-30 10:56 ` Karthik Nayak
2026-09-30 11:59 ` Pablo Sabater
2026-09-30 0:21 ` [PATCH RFC 3/5] fetch-object-info: return a status instead of dying Pablo Sabater
2026-09-30 17:07 ` Junio C Hamano
2026-09-30 18:03 ` Pablo Sabater
2026-09-30 20:01 ` Junio C Hamano
2026-09-30 0:21 ` [PATCH RFC 4/5] backfill: add --dry-run option Pablo Sabater
2026-09-30 11:06 ` Karthik Nayak
2026-09-30 12:19 ` Pablo Sabater
2026-09-30 0:21 ` [PATCH RFC 5/5] backfill: report total size of missing blobs in --dry-run Pablo Sabater
2026-09-30 17:17 ` Junio C Hamano
2026-09-30 18:31 ` Pablo Sabater
2026-09-30 18:14 ` [PATCH RFC 0/5] Add --dry-run option to git-backfill(1) Derrick Stolee
2026-09-30 19:06 ` Pablo Sabater
2026-09-30 20:03 ` Junio C Hamano
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=20260930-backfill-dryrun-v1-1-1128f247ee01@gmail.com \
--to=pabloosabaterr@gmail.com \
--cc=git@vger.kernel.org \
--cc=stolee@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