<div dir="ltr">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.<div><div><div class="gmail_extra">
<br><div class="gmail_quote">On Sat, Dec 5, 2015 at 1:25 PM, Alex Blewitt via swift-dev <span dir="ltr"><<a href="mailto:swift-dev@swift.org" target="_blank">swift-dev@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
> On 5 Dec 2015, at 19:46, Jordan Rose <<a href="mailto:jordan_rose@apple.com">jordan_rose@apple.com</a>> wrote:<br>
><br>
> 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.<br>
<br>
</span>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.<br>
<br>
If you are merging multiple commits there should be at least a build check on each of them instead of only the merge node.<br>
<span class="HOEnZb"><font color="#888888"><br>
Alex<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
swift-dev mailing list<br>
<a href="mailto:swift-dev@swift.org">swift-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-dev</a><br>
</div></div></blockquote></div><br></div></div></div></div>