> This is because "git pull" currently does not know about rebase's > preserve merges flag, which would this behavior, and instead replay > on the merge commit of the feature branch onto the new master, and > not the entire feature branch itself.
Ack, sorry, I was doing this too late last night--should say: This is because "git pull" currently does not know about rebase's preserve merges flag, which would avoid this behavior by replaying the merge commit of the feature branch onto the new master, and not replaying each individual commit in the feature branch. - Stephen -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
