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 instead of fixing the code so that the editing actually works? 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
