From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>,
jvusich@amazon.com, Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH v2] builtin/init-db: handle bare clones when core.bare set to false
Date: Wed, 10 Mar 2021 15:09:32 -0800 [thread overview]
Message-ID: <xmqq7dmeip1v.fsf@gitster.g> (raw)
In-Reply-To: <20210310011120.1151749-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Wed, 10 Mar 2021 01:11:20 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> diff --git a/t/t5606-clone-options.sh b/t/t5606-clone-options.sh
> index 52e5789fb0..c2b71e78c5 100755
> --- a/t/t5606-clone-options.sh
> +++ b/t/t5606-clone-options.sh
> @@ -104,6 +104,14 @@ test_expect_success 'redirected clone -v does show progress' '
>
> '
>
> +test_expect_success 'clone does not segfault with --bare and core.bare=false' '
> + test_config_global core.bare false &&
> + git clone --bare parent clone-bare &&
Because "git clone" does so many different things from the normal
codepath in the "local" codepath, I'd prefer to see this one done
with the "--no-local" option (or alternatively, we could test both,
but that may be overkill).
> + echo true >expect &&
> + git -C clone-bare rev-parse --is-bare-repository >actual &&
> + test_cmp expect actual
> +'
> +
> test_expect_success 'chooses correct default initial branch name' '
> GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME= \
> git -c init.defaultBranch=foo init --bare empty &&
next prev parent reply other threads:[~2021-03-10 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 0:06 bug: conflicting core.bare setting causes segfault during bare clone Vusich, Joseph
2021-03-03 23:59 ` brian m. carlson
2021-03-04 1:13 ` Junio C Hamano
2021-03-04 11:48 ` Vusich, Joseph
2021-03-08 13:17 ` [PATCH] builtin/init-db: handle bare clones when core.bare set to false brian m. carlson
2021-03-08 16:43 ` Eric Sunshine
2021-03-08 23:22 ` brian m. carlson
2021-03-10 1:11 ` [PATCH v2] " brian m. carlson
2021-03-10 23:09 ` Junio C Hamano [this message]
2021-03-10 23:33 ` brian m. carlson
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=xmqq7dmeip1v.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jvusich@amazon.com \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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).