From: "Nathan Froyd via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Nathan Froyd <froydnj@gmail.com>, Nathan Froyd <froydnj@gmail.com>
Subject: [PATCH] builtin/fetch-pack: indicate when we have an exact oid
Date: Thu, 24 Sep 2026 13:50:34 +0000 [thread overview]
Message-ID: <pull.2420.git.git.1790257834680.gitgitgadget@gmail.com> (raw)
From: Nathan Froyd <froydnj@gmail.com>
The `git fetch` path, when parsing OIDs, properly sets `exact_oid` on
the relevant refs; the equivalent path for `git fetch-pack` does not.
This oversight results in an invocation of `git fetch-pack $OID`
sending `want-ref $OID`, which results in errors like:
fatal: unknown ref $OID
fatal: remote error: unknown ref $OID
Make the two paths equivalent by setting `exact_oid` properly.
Signed-off-by: Nathan Froyd <froydnj@gmail.com>
---
builtin/fetch-pack: indicate when we have an exact oid
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2420%2Ffroydnj%2Ffroydnj-fetch-pack-exact-oid-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2420/froydnj/froydnj-fetch-pack-exact-oid-v1
Pull-Request: https://github.com/git/git/pull/2420
builtin/fetch-pack.c | 4 +-
t/t5703-upload-pack-ref-in-want.sh | 68 ++++++++++++++++++++++++++++++
2 files changed, 71 insertions(+), 1 deletion(-)
diff --git a/builtin/fetch-pack.c b/builtin/fetch-pack.c
index 86754296fa..bef8a3dfc5 100644
--- a/builtin/fetch-pack.c
+++ b/builtin/fetch-pack.c
@@ -23,13 +23,14 @@ static void add_sought_entry(struct ref ***sought, int *nr, int *alloc,
struct ref *ref;
struct object_id oid;
const char *p;
+ int exact_oid = 0;
if (!parse_oid_hex(name, &oid, &p)) {
if (*p == ' ') {
/* <oid> <ref>, find refname */
name = p + 1;
} else if (*p == '\0') {
- ; /* <oid>, leave oid as name */
+ exact_oid = 1; /* <oid>, leave oid as name */
} else {
/* <ref>, clear cruft from oid */
oidclr(&oid, the_repository->hash_algo);
@@ -41,6 +42,7 @@ static void add_sought_entry(struct ref ***sought, int *nr, int *alloc,
ref = alloc_ref(name);
oidcpy(&ref->old_oid, &oid);
+ ref->exact_oid = exact_oid;
(*nr)++;
ALLOC_GROW(*sought, *nr, *alloc);
(*sought)[*nr - 1] = ref;
diff --git a/t/t5703-upload-pack-ref-in-want.sh b/t/t5703-upload-pack-ref-in-want.sh
index 330d049b2c..c02e1fc79c 100755
--- a/t/t5703-upload-pack-ref-in-want.sh
+++ b/t/t5703-upload-pack-ref-in-want.sh
@@ -242,6 +242,74 @@ test_expect_success 'fetching with exact OID' '
test_grep "want $oid" log
'
+test_expect_success 'fetch-pack with ref and exact OID from arguments' '
+ test_when_finished "rm -f log" &&
+
+ rm -rf local &&
+ cp -r "$LOCAL_PRISTINE" local &&
+ oid=$(git -C "$REPO" rev-parse d) &&
+ main_oid=$(git -C "$REPO" rev-parse main) &&
+ GIT_TRACE_PACKET="$(pwd)/log" git -C local fetch-pack \
+ "$REPO" refs/heads/main "$oid" >actual &&
+ cat >expected <<-EOF &&
+ $oid $oid
+ $main_oid refs/heads/main
+ EOF
+ sort expected >expected.sorted &&
+ sort actual >actual.sorted &&
+ test_cmp expected.sorted actual.sorted &&
+ git -C local cat-file -e "$oid" &&
+ git -C local cat-file -e "$main_oid" &&
+ test_grep "want $oid" log &&
+ test_grep "want-ref refs/heads/main" log
+'
+
+test_expect_success 'fetch-pack with ref and exact OID from stdin' '
+ test_when_finished "rm -f log" &&
+
+ rm -rf local &&
+ cp -r "$LOCAL_PRISTINE" local &&
+ oid=$(git -C "$REPO" rev-parse d) &&
+ main_oid=$(git -C "$REPO" rev-parse main) &&
+ cat >input <<-EOF &&
+ refs/heads/main
+ $oid
+ EOF
+ GIT_TRACE_PACKET="$(pwd)/log" git -C local fetch-pack \
+ --stdin "$REPO" <input >actual &&
+ cat >expected <<-EOF &&
+ $oid $oid
+ $main_oid refs/heads/main
+ EOF
+ sort expected >expected.sorted &&
+ sort actual >actual.sorted &&
+ test_cmp expected.sorted actual.sorted &&
+ git -C local cat-file -e "$oid" &&
+ git -C local cat-file -e "$main_oid" &&
+ test_grep "want $oid" log &&
+ test_grep "want-ref refs/heads/main" log
+'
+
+test_expect_success 'fetch-pack with OID and ref name resolves the ref' '
+ test_when_finished "rm -f log" &&
+
+ rm -rf local &&
+ cp -r "$LOCAL_PRISTINE" local &&
+ oid=$(git -C "$REPO" rev-parse d) &&
+ main_oid=$(git -C "$REPO" rev-parse main) &&
+ cat >input <<-EOF &&
+ $oid refs/heads/main
+ EOF
+ GIT_TRACE_PACKET="$(pwd)/log" git -C local fetch-pack \
+ --stdin "$REPO" <input >actual &&
+ cat >expected <<-EOF &&
+ $main_oid refs/heads/main
+ EOF
+ test_cmp expected actual &&
+ git -C local cat-file -e "$main_oid" &&
+ test_grep "want-ref refs/heads/main" log
+'
+
test_expect_success 'fetching multiple refs' '
test_when_finished "rm -f log" &&
base-commit: 3bc0341126508f78f5869cbfc0005e987efdf0c7
--
gitgitgadget
next reply other threads:[~2026-09-24 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 13:50 Nathan Froyd via GitGitGadget [this message]
2026-09-25 1:51 ` [PATCH] builtin/fetch-pack: indicate when we have an exact oid Junio C Hamano
2026-09-25 4:40 ` 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=pull.2420.git.git.1790257834680.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=froydnj@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.