[swift-dev] Merge-commit noise?
Alex Blewitt
alex.blewitt at gmail.com
Sat Dec 5 15:25:44 CST 2015
> On 5 Dec 2015, at 19:46, Jordan Rose <jordan_rose at apple.com> wrote:
>
> Because not everyone submitting a patch has necessarily maintained that rigor (particularly not after rebasing), we use the merge commit to make multiple out-of-tree commits atomic.
Having a merge commit in this way doesn't mean that you avoid bisect problems in any way. It means you are more likely to find a bad commit.
If you are merging multiple commits there should be at least a build check on each of them instead of only the merge node.
Alex
More information about the swift-dev
mailing list