Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    According to the rebase man page, Note that any commits in HEAD which introduce the same textual changes as a commit in HEAD..<upstream> are omitted (i.e., a patch already accepted upstream with a different commit message or timestamp will be skipped). your proposed command should work fine. Commented Sep 18, 2015 at 13:32
  • Hmm... I didn't realise that. I may be confused about what's causing my rebases to fail. I'll investigated and come back to this question. Thanks Commented Sep 18, 2015 at 13:46
  • 1
    you might get conflicts when your E' or F' were merged with conflicts as the diff will change. Commented Sep 18, 2015 at 19:16
  • OK, I've realised that the reason this is happening (rather obviously, it now seems), is when I modify E' so it no longer introduces the same changes as E. It doesn't happen for every commit. The solutions seems to be to just use git rebase --skip in those cases. Commented Sep 21, 2015 at 10:02