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

Re: receive.denyCurrentBranch=updateInstead won't update the repo

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 18, 2023, 23:03 UTC
Message-ID
<xmqqh6q0esbd.fsf@gitster.g>
In-Reply-To
<CAGE71k28Gao4xuR565qsLmPH02tVAdoCZPeuCjo7r9YZXWs82Q@mail.gmail.com>
"Adam \"Sinus\" Skawiński"  <adam.skawinski@sinpi.net> writes:
> Oh. Then it's different from the other hooks, which merely enhance or
> abort the default behaviour by returning non-zero! I hadn't thought of
> that.

I do not know if it is all that different from others, but in any case it is a clear sign that the documentation needs a bit more love to make sure that it will not lead new readers and users into the same confusion.

Thanks.
Previous: Adam Sinus SkawińskiNext: Adam Sinus Skawiński
Message 8 of 9 in “receive.denyCurrentBranch=updateInstead won't update the repo”
  1. Adam Sinus SkawińskiJul 17, 2023
  2. Junio C HamanoJul 17, 2023
  3. Junio C HamanoJul 17, 2023
  4. Adam Sinus SkawińskiJul 17, 2023
  5. Adam Sinus SkawińskiJul 18, 2023
  6. Junio C HamanoJul 18, 2023
  7. Adam Sinus SkawińskiJul 18, 2023
  8. Junio C HamanoJul 18, 2023
  9. Adam Sinus SkawińskiJul 18, 2023

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.