From: "Vusich, Joseph" <jvusich@amazon.com>
To: Junio C Hamano <gitster@pobox.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: bug: conflicting core.bare setting causes segfault during bare clone
Date: Thu, 4 Mar 2021 11:48:27 +0000 [thread overview]
Message-ID: <6962C073-60A9-4FCB-8FAA-02549A78547D@amazon.com> (raw)
In-Reply-To: <xmqq4khrg1qx.fsf@gitster.c.googlers.com>
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> I will admit being a bit interested in how this was discovered, since it
> seems like an odd configuration to have, so if you can share, I'd
> appreciate it, if only to satisfy my curiosity.
Quite by accident. A machine-generated .gitconfig with some "default"
values, which inadvertently included core.bare=false.
> "Junio C Hamano" <gitster@pobox.com> wrote:
> I had the same reaction. Forcing everything to be bare is quite
> unusual.
Technically non-bare in this case, although the field seems to be ignored
in the global config, at least prior to Git 2.30.0. In any case, it never
had any observable effect, and was therefore never noticed.
next prev parent reply other threads:[~2021-03-04 11:51 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 [this message]
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
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=6962C073-60A9-4FCB-8FAA-02549A78547D@amazon.com \
--to=jvusich@amazon.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/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).