Re: [PATCH v4] Allow update hooks to update refs on their own.

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 3, 2007, 05:25 UTC
Message-ID: <7vmyssqrhk.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20071203040108.GS14735@spearce.org>

"Shawn O. Pearce" <spearce@spearce.org> writes:

> This probably requires exporting the name of the ref we currently
> have locked in an environment variable (and teach lockfile.c it)
> so we can effectively do recursive locking.  That way the update
> hook can still use git-update-ref to change the ref safely.

Heh, I like that, although I suspect getting this right would mean the topic should be post 1.5.4 (which I do not mind).

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