diff options
| author | Jeff King <peff@peff.net> | 2025-03-08 22:02:03 -0500 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2025-03-10 13:13:45 -0700 |
| commit | 6ea26f34c95a333d633e2b691805df0c62e6d568 (patch) | |
| tree | cb02ab466183b8a8fad39900148635f865214df5 /t/t5516-fetch-push.sh | |
| parent | t5516: prefer "oid" to "sha1" in some test titles (diff) | |
| download | git-6ea26f34c95a333d633e2b691805df0c62e6d568.tar.gz git-6ea26f34c95a333d633e2b691805df0c62e6d568.zip | |
t5516: drop NEEDSWORK about v2 reachability behavior
When this test was added in 6c301adb0a (fetch: do not pass ref-prefixes
for fetch by exact SHA1, 2018-05-31), there was still some uncertainty
about the v2 protocol's looser behavior with serving objects that are
not directly pointed at by a ref.
At this point that behavior is well established, and I do not think we
would ever change v2 to match the v0 behavior (and if we did,
remembering to update this test is the least of our concerns).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5516-fetch-push.sh')
| -rwxr-xr-x | t/t5516-fetch-push.sh | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh index e7629fc536..e4008f3ca6 100755 --- a/t/t5516-fetch-push.sh +++ b/t/t5516-fetch-push.sh @@ -1312,7 +1312,6 @@ test_expect_success 'fetch exact oid in protocol v2' ' test_must_fail git -C child cat-file -t $the_commit && # fetching the hidden object succeeds by default - # NEEDSWORK: should this match the v0 behavior instead? git -C child fetch -v ../testrepo $the_commit:refs/heads/copy ' |
