git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
BFBrian Foster <brian.foster@innova-card.com>
Date
Jun 16, 2008, 12:36 UTC
Message-ID
<200806161436.37278.brian.foster@innova-card.com>
 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
Next: Johannes Schindelin
Message 1 of 2 in “no `bare = true' in `config' of a bare repository - problem or ignore?”
  1. Brian FosterJun 16, 2008
  2. Johannes SchindelinJun 17, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.