From: Vincent van Ravesteijn <vfr@lyx.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: git@vger.kernel.org
Subject: Re: rebase problem
Date: Sat, 17 Mar 2012 14:30:42 +0100 [thread overview]
Message-ID: <4F649202.4080102@lyx.org> (raw)
In-Reply-To: <OF506B5658.3E449452-ONC12579C4.00460A6E-C12579C4.0047355D@transmode.se>
Op 17-3-2012 13:57, Joakim Tjernlund schreef:
> A co-worker this on our local u-boot repo:
> git checkout master
> git fetch denx/master
> git merge denx/master
> <resolve conflicts>
> git commit
> ...
> git commit
> Now u-boot is working again
> then update to latest u-boot so:
> git fetch denx/master
> git rebase denx/master
> Now it is a mess, that rebase seems to start from way back as a
> staring reference, not from the last merge shown above.
> I guess I forgotten how git works, what did go wrong?
>
> Jocke
>
> --
> 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
The situation is like this:
master - C - o - o - D - o - o - o - A
/
denx/master- - - - o - o - o - o - B
Now, you ask to rebase master (A) onto denx/master (B). If master would
have started from D, it would indeed apply the commits D -- A on top of
B. In your case, however, master already had a lot of commits that were
not in denx/master: C -- D (including the merge resolution). So it will
also apply C -- D on top of B.
Vincent
next prev parent reply other threads:[~2012-03-17 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 12:57 rebase problem Joakim Tjernlund
2012-03-17 13:30 ` Vincent van Ravesteijn [this message]
2012-03-17 14:31 ` Joakim Tjernlund
2012-03-17 16:11 ` Vincent van Ravesteijn
2012-03-17 16:55 ` Joakim Tjernlund
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=4F649202.4080102@lyx.org \
--to=vfr@lyx.org \
--cc=git@vger.kernel.org \
--cc=joakim.tjernlund@transmode.se \
/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).