no `bare = true' in `config' of a bare repository - problem or ignore?

Brian Foster· Jun 16, 2008, 12:36 UTC · lore

 Whilst investigating a (probably unrelated) mystery,
 I noticed that some of my bare git repositories had:

	[core]
 	    bare = true

 whilst others did not (they had no `bare' setting at
 all).  All, with or without `bare', seem to be quite
 happy, but I was wondering what's going on;  is this
 a problem;  and if not, is there any point to adding
 the setting anyways?

 As to _why_ some do and some don't, I haven't a clew,
 but suspect the ones that do NOT were originally made
 with an (unknown) older version of git;  and the ones
 that do were made with git 1.5.3 or later.

 The git-config(1) man page (1.5.5) doesn't directly
 mention this, only talking about auto-guessing the
 value on init and clone.  Apologies if TFM explains;
 I didn't spot anything.

cheers!
	-blf-

-- 
“How many surrealists does it take to   | Brian Foster
 change a lightbulb? Three. One calms   | somewhere in south of France
 the warthog, and two fill the bathtub  |   Stop E$$o (ExxonMobil)!
 with brightly-coloured machine tools.” |      http://www.stopesso.com

Johannes Schindelin· Jun 17, 2008, 09:25 UTC · re: Brian Foster · lore

Re: no `bare = true' in `config' of a bare repository - problem or ignore?

Hi,

On Mon, 16 Jun 2008, Brian Foster wrote:

Show 8 quoted lines

>  Whilst investigating a (probably unrelated) mystery,
>  I noticed that some of my bare git repositories had:
> 
> 	[core]
>  	    bare = true
> 
>  whilst others did not (they had no `bare' setting at
>  all).

It's a historical thing: this setting was not present in older Git. Basically, we still have some autodetection ignoring the absence of core.bare.

Shouldn't be a problem.

Ciao, Dscho