> I don't remember all the arguments; but the point that stuck with me was > that such rebases are generally untested, >
Nothing goes into master without being tested in the form master will be post-merge > Automatic patch merging works out surprisingly often -- but sometimes it > doesn't. If there is a bad merge commit, `git bisect` will clearly point > to it as the culprit; while problems introduced in a rebase will in no > way indicate the rebase as the cause. > note that git bisect gets rather muddled with merge commits unless you teach it to only bisect over merges. -Manish Goregaokar _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
