Re: [PATCH 4/5] Add --remote option to send-pack

["Shawn O. Pearce" <spearce@spearce.org>]

Daniel Barkalow <barkalow@iabervon.org> wrote:
> We're not pretending anything; remote has confirmed that the head that the 
> ref tracks has a particular new value (which we provided), so we should be 
> able to update the tracking ref to that value. I don't think it's 
> particularly important that we came by this information in the course of 
> an exchange that wasn't a fetch.

s/remote has confirmed/remote has claimed/

The only way to know the remote really did remember that
refs/heads/foo is now at 3c1718... is to perform some sort of
operation against it that makes it dump its refs back.  Trying to
push again, or trying to fetch does that.

There is also the possibility that a post-update or post-receive
hook will actually modify the ref *after* the push is "complete".
But that's like so crazy that I really don't think anyone has a
workflow that does that.  They might have such a hook that creates
a new ref however, or updates a totally unrelated ref (e.g. compile
the code and then update a "last-built" ref).

So in this particular case I have to agree with Daniel, its probably
OK to do what Cogito does and update the tracking branch after the
push was claimed to be successful by the remote.

-- 
Shawn.