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

Bug: receive.denyCurrentBranch fails if core.bare unset

From
ACAlban Crequy <alban.crequy@collabora.co.uk>
Date
Jun 12, 2009, 15:53 UTC
Message-ID
<20090612185318.42e738c6@alban.research.nokia.com>
Hi,

When I set "receive.denyCurrentBranch" to "refuse", it still have the behavior of ignore. On newly created repository, core.bare is always set, but I had a old non-bare repository where it is unset. With core.bare unset, rev-parse --is-bare-repository returns true in .git, but false in the worktree.

What should be the right fix for this problem? Adding in the documentation of receive.denyCurrentBranch that setting core.bare explicitely is highly recommended ?

Br, Alban

Message 1 of 1 in “Bug: receive.denyCurrentBranch fails if core.bare unset”
  1. Alban CrequyJun 12, 2009

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.