Re: pull/push inconsistencies

From: J. Bruce Fields <bfields@fieldses.org>
Date: May 16, 2007, 01:40 UTC
Message-ID: <20070516014002.GA8062@fieldses.org>
In-Reply-To: <7v646th8a2.fsf@assigned-by-dhcp.cox.net>

On Tue, May 15, 2007 at 06:22:29PM -0700, Junio C Hamano wrote:

Show 14 quoted lines

> "Martin Langhoff" <martin.langhoff@gmail.com> writes:
> 
> > There are 2 things that I see as wrong...
> > - local .git/refs/remote/origin/foo and refs/heads/foo match - why is
> > git-push talking about updating them?
> 
> Ooo...
> 
> Do you mean if you have refs/remotes/origin/foo locally, and
> push into a repository that has refs/heads/foo (but not
> refs/remotes/origin/foo), the push results in refs/heads/foo
> getting updated?  If that is what is happening (without any
> refspecs to instruct git-push to do so) that sounds quite buggy.
> I need to look into the code for this one.

I understand him to be saying that it *doesn't* do that, and that he *wants* it to.

People think of refs/remotes/origin as a cache of the origin repository's branch heads, and they expect it to be updated on write (push) as well as read (fetch).

--b.