From: Junio C Hamano <gitster@pobox.com>
To: Tom Hughes <tom@compton.nu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] push: don't fetch commit object when checking existence
Date: Wed, 22 May 2024 13:55:52 -0700 [thread overview]
Message-ID: <xmqqed9t36sn.fsf@gitster.g> (raw)
In-Reply-To: <20240522201559.1677959-1-tom@compton.nu> (Tom Hughes's message of "Wed, 22 May 2024 21:15:40 +0100")
Tom Hughes <tom@compton.nu> writes:
> diff --git a/t/t0410-partial-clone.sh b/t/t0410-partial-clone.sh
> index 88a66f0904..7797391c03 100755
> --- a/t/t0410-partial-clone.sh
> +++ b/t/t0410-partial-clone.sh
> @@ -689,6 +689,25 @@ test_expect_success 'lazy-fetch when accessing object not in the_repository' '
> ! grep "[?]$FILE_HASH" out
> '
>
> +test_expect_success 'push should not fetch new commit objects' '
> + rm -rf server client &&
> + test_create_repo server &&
> + test_config -C server uploadpack.allowfilter 1 &&
> + test_config -C server uploadpack.allowanysha1inwant 1 &&
> + test_commit -C server server1 &&
OK, we create the source that allows a partial clone.
> + git clone --filter=blob:none "file://$(pwd)/server" client &&
> + test_commit -C client client1 &&
And make a clone out of it, without blobs.
> + test_commit -C server server2 &&
> + COMMIT=$(git -C server rev-parse server2) &&
Then we create a new commit that the client does not yet have.
> + test_must_fail git -C client push 2>err &&
We try to overwrite it. We expect it to fail with "not a fast forward".
> + grep "fetch first" err &&
May want to use "test_grep" but this script does not use it, so
being consistent with the surrounding tests is good.
> + git -C client rev-list --objects --missing=print "$COMMIT" >objects &&
> + grep "^[?]$COMMIT" objects
> +'
OK.
> . "$TEST_DIRECTORY"/lib-httpd.sh
> start_httpd
Looking good. Thanks, will queue.
next prev parent reply other threads:[~2024-05-22 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 13:36 [PATCH] push: don't fetch commit object when checking existence Tom Hughes
2024-05-22 19:16 ` Junio C Hamano
2024-05-22 20:15 ` [PATCH v2] " Tom Hughes
2024-05-22 20:55 ` Junio C Hamano [this message]
2024-05-22 21:46 ` Tom Hughes
2024-05-22 21:58 ` Junio C Hamano
2024-05-23 8:58 ` Jeff King
2024-05-22 20:18 ` [PATCH] " Tom Hughes
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=xmqqed9t36sn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tom@compton.nu \
/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;
as well as URLs for NNTP newsgroup(s).