Re: bug: conflicting core.bare setting causes segfault during bare clone

From: Vusich, Joseph <jvusich@amazon.com>
Date: Mar 4, 2021, 11:48 UTC
Message-ID: <6962C073-60A9-4FCB-8FAA-02549A78547D@amazon.com>
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.