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

From: Steven Grimm <koreth@midwinter.com>
Date: Nov 28, 2007, 20:16 UTC
Message-ID: <C1321BD5-8F6B-47F9-9BDB-C2BF819D6F17@midwinter.com>
In-Reply-To: <20071128194919.GC11396@coredump.intra.peff.net>

On Nov 28, 2007, at 11:49 AM, Jeff King wrote:

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

Ah, yes, I see what you mean. Okay, please ignore my latest patch -- I will redo it on top of "next" later today/tonight.

Well, actually, I would still like opinions on one thing: What do people think of having git-push do a fetch if the remote side changes a ref to point to a revision that doesn't exist locally? Is there a situation where you'd ever want to *not* do that?

-Steve