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

Re: "warning: Updating the currently checked out branch may cause confusion" on bare repositories

From
AMAdam Megacz <adam@megacz.com>
Date
Jan 19, 2010, 18:55 UTC
Message-ID
<xuu2my093owy.fsf@nowhere.com>
In-Reply-To
<20100119062904.GB23212@spearce.org>
"Shawn O. Pearce" <spearce@spearce.org> writes:
> That should already be the case.  Did you create the bare repository
> by taking a copy of a non-bare's .git directory?  Check your bare
> repository's config file and see if core.bare = false, if so set
> it to true to signal it really is bare.

Hrm, is there a reason why this is explicitly configured rather than detected?

I was under the impression that you could create a bare repository by simply throwing away the working tree and renaming ".git" to any other name, but I guess I was wrong.

  - a
Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 3 of 5 in “"warning: Updating the currently checked out branch may cause confusion" on bare repositories”
  1. Adam MegaczJan 18, 2010
  2. Shawn O. PearceJan 19, 2010
  3. Adam MegaczJan 19, 2010
  4. Shawn O. PearceJan 19, 2010
  5. Jeff KingJan 19, 2010

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.