From: Junio C Hamano <gitster@pobox.com>
To: Irene Ros <imirene@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: branch ahead in commits but push claims all up to date
Date: Tue, 24 Mar 2009 09:12:18 -0700 [thread overview]
Message-ID: <7vskl2293x.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7001b7a00903240822w70a57349xcc66a02cef62dc70@mail.gmail.com> (Irene Ros's message of "Tue, 24 Mar 2009 11:22:45 -0400")
Irene Ros <imirene@gmail.com> writes:
> 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.
>
> 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
How does your
[remote "origin"]
part look like?
next prev parent reply other threads:[~2009-03-24 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7001b7a00903240821v2155d234x6a10c80a3e987acb@mail.gmail.com>
2009-03-24 15:22 ` branch ahead in commits but push claims all up to date Irene Ros
2009-03-24 16:12 ` Junio C Hamano [this message]
2009-03-24 16:18 ` John Tapsell
2009-03-24 17:13 ` Daniel Barkalow
2009-03-25 0:26 ` John Tapsell
2009-03-25 1:24 ` Daniel Barkalow
2009-03-25 2:01 ` Irene Ros
2009-03-25 2:13 ` John Tapsell
2009-03-25 3:19 ` Daniel Barkalow
2009-03-25 17:23 ` Irene Ros
2009-03-25 17:32 ` Santi Béjar
2009-03-26 2:05 ` John Tapsell
2009-03-26 12:48 ` Björn Steinbrink
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vskl2293x.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=imirene@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).