Re: branch ahead in commits but push claims all up to date

From: John Tapsell <johnflux@gmail.com>
Date: Mar 24, 2009, 16:18 UTC
Message-ID: <43d8ce650903240918q2ffdba44w241e0f378a11fd3d@mail.gmail.com>
In-Reply-To: <7001b7a00903240822w70a57349xcc66a02cef62dc70@mail.gmail.com>

2009/3/24 Irene Ros <imirene@gmail.com>:

Show 10 quoted lines

> 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 :-)

John

Show 25 quoted lines

> Oddly, when I try to do a push, I get a message saying that everything
> is up to date:
> $ git push origin myBranch
> Everything up-to-date
>
> Looking at the log for origin/myBranch I can tell those commits are
> missing, but I can't push them up, even with a --force flag. Any
> ideas?
> Here's the config entry for this branch:
>
> [branch "myBranch"]
>     remote = origin
>     merge = refs/heads/myBranch
>
> There's also nothing to pull from this branch, I'm the only one working on it.
> I use many other branches in this particular repo, and its just this
> one that's giving me trouble.
>
> Thanks so much!
> -- Irene
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>