On 2008.03.22 15:06:48 +0100, Jörg Sommer wrote: > Björn Steinbrink schrieb am Sat 22. Mar, 02:52 (+0100): > > On 2008.03.22 02:19:42 +0100, Jörg Sommer wrote: > > > The current version of git-rebase--interactive shows the user the commits > > > coming from a merge. > > > > > > M---A---B > > > \ \ > > > o---o---+---o branch > > > > > > Rebasing branch on M with preserve merges gives the commits A and B. But > > > if you mark them for editing or remove them the rebase fails. You must > > > keep them as they are. It's useless to bother the user with these commits > > > and might lead to mistakes. > > > > Uhm, why do you completely remove the possibility to edit A > > Ahh, now I see what you've tried to say. I did add the option > --first-parent for rebase interactive *without* preserve merges, too. > I'll update my patch. I didn't even look at it closely enough to notice that. --preserve-merges preserves the structure of the history. You seem to interpret it as to preserve the merges against the original parents, except for the first one, and that's simply not what it's meant to do. I can see how that might be useful, but you'd have to add that as an additional mode of operation, and not break the normal one. Björn -- 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
