> > # A --C------ <-- origin/stable > > # \ | \ > > # B -- D -- E -- F <-- origin/topic2 > > # \| > > # g -- h <-- topic2 > > > > Nothing has changed. g & h haven't moved...I can keep executing this > > operation and the commits never make it on top of origin/topic2's F. > > > > Frustratingly, if I run non-interactive rebase, it works perfectly. > > I can imagine. Since you don't want to preserve the merges in this > case, you shouldn't be using the -p flag. No, I do want to preserve most merges. This "most" qualification is because the merge "g", if rebased, would have been a no-op, so `rebase -i -p` correctly kept it out of the TODO file. Which is cool, except that later on, when rewriting the other TODO commits, some of which were children of "g", it did not remember that "g" had gone away, so did nothing to take "g" out of the rewritten children's parent list. > In fact, for this particular scenario (assuming "h" is really the only > commit on topic2), you probably want to just cherry-pick that commit > into origin/topic2: > > git checkout topic2 > git reset --hard origin/topic2 > git cherry-pick ORIG_HEAD Agreed. This makes a lot of sense for me, who has been hacking around in git-rebase--interactive fixing things, but I'd really like the other people on my team to just have to run `git rebase -i -p`. > I don't think you can have a single command that does all the things > you want, because the possible differences in input makes it very > nearly impossible to always do "the right thing". Ah, you are too pessimistic. :-) > Assuming you're passing a correct input file to rebase -i; yes. At the > very least, "h" should be moved to the tip of origin/topic2. Cool, agreed. I've got a patch that gets `rebase -i -p` to do this. I'll send it to the list soon. - Stephen -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
