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

From: Jeff King <peff@peff.net>
Date: Nov 28, 2007, 19:49 UTC
Message-ID: <20071128194919.GC11396@coredump.intra.peff.net>
In-Reply-To: <20071128194159.GA25977@midwinter.com>

On Wed, Nov 28, 2007 at 11:41:59AM -0800, Steven Grimm wrote:

> recieve-pack will now send the post-update SHA1 back to send-pack. If
> it's different than the one that was pushed, git-push won't do the
> fake update of the local tracking ref and will instead inform the user
> that the tracking ref needs to be fetched.

Hrm, this is going to have nasty conflicts with 'next', which already does the remote ref matching. I think the best way to implement this would probably be on top of the jk/send-pack topic in next, and add a new REF_STATUS_REMOTE_CHANGED status type.

-Peff

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