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

2 messages, 2 authors, 2021-03-04 · open the first message on its own page

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

From: Junio C Hamano <hidden>
Date: 2021-03-04 01:15:22

"brian m. carlson" [off-list ref] 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.
I had the same reaction.  Forcing everything to be bare is quite
unusual.

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

From: Vusich, Joseph <hidden>
Date: 2021-03-04 11:50:24

"brian m. carlson" [off-list ref] 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" [off-list ref] 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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help