[swift-dev] Merge-commit noise?

[Jacob Bandes-Storch]

Note that recording the original contributor is exactly what happens when
you do `git rebase`: the rebaser will become the Committer, but the Author
remains the same.

On Sat, Dec 5, 2015 at 1:25 PM, Alex Blewitt via swift-dev <
swift-dev at swift.org> wrote:

>
>
> > 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
> _______________________________________________
> swift-dev mailing list
> swift-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-dev/attachments/20151205/6ca0949e/attachment.html>