From: Daniel Barkalow <barkalow@iabervon.org>
Date: Tue, 24 Mar 2009 17:13:03 GMT
Subject: Re: branch ahead in commits but push claims all up to date
Message-ID: <alpine.LNX.1.00.0903241304090.19665@iabervon.org>
In-Reply-To: <43d8ce650903240918q2ffdba44w241e0f378a11fd3d@mail.gmail.com>

On Tue, 24 Mar 2009, John Tapsell wrote:

> 2009/3/24 Irene Ros <imirene@gmail.com>:
> > Hi all,
> >
> > I've been using git for some time now and haven't run into this issue
> > before, perhaps someone else here has:
> >
> > I have a branch that is ahead of its origin by a few commits:
> >
> > $ git status
> > # On branch myBranch
> > # Your branch is ahead of 'origin/myBranch' by 10 commits.
> 
> Tried running: git fetch   ?
> 
> For some weird reason  "git push origin mybranch"  doesn't actually
> update origin/mybranch.  It's more annoying :-)

It should, so long as you're using the native transport and 
origin/mybranch actually tracks mybranch on origin.

"git push" doesn't update it, but the code that implements the native 
transport does update it if it succeeds.

(Actually, I'm not 100% sure that, if you update origin through some other 
channel with exactly the commit that you now have in mybranch locally, and 
then try the push, it will update the local tracking for that branch; is 
that what you've hit?)

	-Daniel
*This .sig left intentionally blank*