From: Junio C Hamano <gitster@pobox.com>
To: "Øystein Walle" <oystwa@gmail.com>
Cc: avarab@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH v2] clone: Allow combining --bare and --origin
Date: Tue, 03 Aug 2021 18:16:49 -0700 [thread overview]
Message-ID: <xmqqzgtyqa9q.fsf@gitster.g> (raw)
In-Reply-To: <20210802174944.53745-1-oystwa@gmail.com> ("Øystein Walle"'s message of "Mon, 2 Aug 2021 19:49:44 +0200")
Øystein Walle <oystwa@gmail.com> writes:
> diff --git a/t/t5606-clone-options.sh b/t/t5606-clone-options.sh
> index 3a595c0f82..c40dde816d 100755
> --- a/t/t5606-clone-options.sh
> +++ b/t/t5606-clone-options.sh
> @@ -30,12 +30,12 @@ test_expect_success 'rejects invalid -o/--origin' '
>
> '
>
> -test_expect_success 'disallows --bare with --origin' '
> -
> - test_must_fail git clone -o foo --bare parent clone-bare-o 2>err &&
> - test_debug "cat err" &&
> - test_i18ngrep -e "--bare and --origin foo options are incompatible" err
> +test_expect_success '--bare works with -o/--origin' '
>
> + git clone --bare --origin=somewhere parent clone-bare &&
> + url="$(git -C clone-bare config --local remote.somewhere.url)" &&
> + test -n "$url" &&
> + test_must_fail git -C clone-bare config --local remote.origin.url
> '
This breaks a later step that creates clone-bare as this used to use
clone-bare-o and the name was available.
Using clone-bare-o as it used to would probably be the easiest fix.
>
> test_expect_success 'disallows --bare with --separate-git-dir' '
prev parent reply other threads:[~2021-08-04 1:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 8:25 [PATCH] clone: Remove constraint on --bare and --origin Øystein Walle
2021-08-02 2:18 ` Junio C Hamano
2021-08-02 8:53 ` Ævar Arnfjörð Bjarmason
2021-08-02 17:49 ` [PATCH v2] clone: Allow combining " Øystein Walle
2021-08-03 21:28 ` Junio C Hamano
2021-08-04 13:30 ` Øystein Walle
2021-08-04 17:06 ` Junio C Hamano
2021-08-06 20:23 ` Roman Neuhauser
2021-08-06 22:13 ` Junio C Hamano
2021-08-07 11:18 ` Roman Neuhauser
2021-08-07 22:08 ` Re* " Junio C Hamano
2021-08-08 2:03 ` Roman Neuhauser
2021-08-04 1:16 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqzgtyqa9q.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=oystwa@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).