Dale Worley <[email protected]> writes: >> From: Junio C Hamano <[email protected]> >> >> I think this is to be expected for "git rebase", as it does not even >> look at merges. It is a way to find non-merge commits that haven't >> been applied yet, and apply them to the upstream to create a new >> linear history. > > I disagree. "git rebase" is not characterized as ...
The intention has always been "I have these patches, some were applied upstream already, now what do I have left?". You do realize that you are disagreeing with somebody who designed the original "git rebase" (before the --preserve-merges was added), do you? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
