<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 12, 2016, at 4:52 PM, Chandler Carruth <<a href="mailto:chandlerc@gmail.com" class="">chandlerc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_quote"><div dir="ltr" class="">On Fri, Feb 12, 2016 at 3:58 PM Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">On Feb 12, 2016, at 2:29 PM, Philip Reames <<a href="mailto:listmail@philipreames.com" target="_blank" class="">listmail@philipreames.com</a>> wrote:</div><div style="word-wrap:break-word" class=""><div class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class="">If so, that would resolve the licensing concern. In
the future, let's make sure that gets mentioned in the review/commit
thread to avoid confusion.<br class=""></div></div></blockquote><div class=""><br class=""></div></div></div><div style="word-wrap:break-word" class=""><div class=""><div class="">I can understand your concern, but for better or worse, we don’t ask llvm contributors to state the provenance of their code that they are posting. If you’re asking for some new rule to be put in place, please specify what the rule is and what the rationale for that rule is.</div></div></div></blockquote><div class=""><br class=""></div><div class="">I don't want to speak for Philip, but I think the thing that made this a bit different was the explicit statement that the code came from some particular source (a different open source project in this case) and that triggered a concern about whether it was reasonable to contribute it. That doesn't seem unreasonable.</div><div class=""><br class=""></div><div class="">For example, when someone contributed a patch from the GCC fork of the sanitizer runtimes, we asked similar questions to what Philip has asked here because the statement that the patch came from somewhere else seemed directly in conflict with the contributor being able to correctly contribute it to LLVM.</div></div></div></div></blockquote><br class=""></div><div>Ok, yes, I think it makes sense for someone moving code from one project to the other to reassure that they have the rights to do so.</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>