> >> Come on! Please, please, explain me why it behaves DIFFERENTLY: >> >> esajine@ESAJINEWWW /c/git_repos/test2 (topic) >> $ git rebase --onto master topic >> First, rewinding head to replay your work on top of it... >> fatal: Not a range. >> Nothing to do. >> <======== topic..HEAD is not a range, agreed >> >> >> esajine@ESAJINEWWW /c/git_repos/test2 (topic) >> $ git rebase -i --onto master topic >> Successfully rebased and updated refs/heads/topic. <=== BUG – here it >> printed me “noop” in file to edit, when I exited it should do nothing, >> but it still did something and I double checked it. > > A historical accident, so to say. The implementor of interactive rebase > felt the "noop" behavior was useful, and I agree, FWIW. > > -- Hannes > IMHO this "noop" behavior seems to be identical to "git reset --hard master" - the result is the same. Frankly, I don't understand what is useful in such thing being HIDDEN in "incorrect call" of interactive rebase... Thanks, Eugene -- 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