From: PJ Weisberg <pj@irregularexpressions.net>
To: Hilco Wijbenga <hilco.wijbenga@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Your branch and 'origin/master' have diverged
Date: Tue, 14 Aug 2012 09:02:29 -0700 [thread overview]
Message-ID: <CAJsNXTmUB-isPVHPcWupL-gAag--DzhdkazXj0Z+aEbv+_w7Rg@mail.gmail.com> (raw)
In-Reply-To: <CAE1pOi1WTbMSK8dOus6pFCa2C9vGA8QNE3+8w0LFmGkvcfq5fg@mail.gmail.com>
On Mon, Aug 13, 2012 at 12:58 PM, Hilco Wijbenga
<hilco.wijbenga@gmail.com> wrote:
> Hi all,
>
> A colleague of mine (after a relatively long absence) noticed the
> following when running "git status":
>
> # On branch master
> # Your branch and 'origin/master' have diverged,
> # and have 250 and 19 different commit(s) each, respectively.
> #
> nothing to commit (working directory clean)
>
> He asked me what to do and I told him to do what has always worked for
> me in the past when something like this happened: gitk, "reset master
> branch to here" (to a commit before the divergence and using --hard),
> git pull origin master. Problem solved.
>
> Well, not this one. This one is persistent. :-) I am at a loss what to
> do. "master" and "origin/master" do *not* point at the same commit.
> Even after the "git reset --hard ..." and "git pull". Running my
> silver bullet solution gets us in the same situation every time.
I assume that the commit you reset to wasn't actually before the
divergence, then. It sounds like what you're trying to do is just
long-hand for 'git reset --hard origin/master'. As mentioned before,
that *does* assume that you want to throw out everything you've
committed locally. If that's *not* the case, try 'git rebase
origin/master' or 'git pull --rebase'. And then go slap the person
who rewrote the history of origin/master.
-PJ
Gehm's Corollary to Clark's Law: Any technology distinguishable from
magic is insufficiently advanced.
next prev parent reply other threads:[~2012-08-14 16:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 19:58 Your branch and 'origin/master' have diverged Hilco Wijbenga
2012-08-14 8:27 ` Thomas Rast
2012-08-14 17:04 ` Hilco Wijbenga
2012-08-14 17:19 ` Junio C Hamano
2012-08-14 18:32 ` Hilco Wijbenga
2012-08-14 18:49 ` Junio C Hamano
2012-08-14 20:12 ` Thomas Rast
2012-08-14 20:49 ` Junio C Hamano
2012-08-15 6:59 ` Thomas Rast
2012-08-15 17:30 ` Junio C Hamano
2012-08-15 18:38 ` Holger Hellmuth (IKS)
2012-08-15 19:07 ` Junio C Hamano
2012-08-15 19:22 ` Junio C Hamano
2012-08-16 16:24 ` Jeff King
2012-08-16 17:57 ` Junio C Hamano
2012-08-16 16:21 ` Jeff King
2012-08-14 22:15 ` Hilco Wijbenga
2012-08-14 22:35 ` Junio C Hamano
2012-08-14 16:02 ` PJ Weisberg [this message]
2012-08-14 17:07 ` Hilco Wijbenga
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=CAJsNXTmUB-isPVHPcWupL-gAag--DzhdkazXj0Z+aEbv+_w7Rg@mail.gmail.com \
--to=pj@irregularexpressions.net \
--cc=git@vger.kernel.org \
--cc=hilco.wijbenga@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).