On Wed, 24 Jun 2015 11:06:52 -0700 (PDT) Konrád Lőrinczi <klorin...@gmail.com> wrote:
> $ git rebase --root --onto orig dev > First, rewinding head to replay your work on top of it... > Applying: E > Applying: F > > > The result is: > A---B---C orig > \ > E---F dev > Still missing the "D" root of dev. Can you proof that "dev" indeed has that D commit? I mean, miracles are rare and far in between so I'd rather beleive you're misinterpreting what's in your *real* history. The thing is, --onto and --root disable the rebase's default logic for figuring out what part of the tree to be rebased to pick and where to tuck it onto. Basically, it's just like saying "don't be smart, do what I said, period". So to me, it really looks like there's no that "D" commit. What happens if you do git rev-list dev ? Does it really show you all the commits you need? -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
