Re: [PATCH 1/2] Add a few more values for receive.denyCurrentBranch

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 12, 2014, 18:00 UTC
Message-ID: <xmqqsiho47uq.fsf@gitster.dls.corp.google.com>
In-Reply-To: <alpine.DEB.1.00.1411121209330.13845@s15462909.onlinehome-server.info>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 6 quoted lines

> Okay, here is my explanation: at the time I wanted to disprove that
> updateInstead could make sense, I wanted to offer a milder version of
> updating the current branch that left the working directory alone:
> detachInstead.
>
> Now, I never used it myself, but I use updateInstead extensively.

Sounds like updateInstead turned out to be useful enough to make a "possibly more cautious" detachInstead unnecessary? It probably makes sense not to add it in that case, I would think.

$ 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.