<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I would say that we've found a reasonable solution, and that we
should run with it. I see minimal value in trying to optimize
this situation further.</p>
<p>Philip<br>
</p>
<div class="moz-cite-prefix">On 7/9/20 1:33 AM, Mike Forster via
llvm-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAZgYSRo6Hvk752rYtPoPAgX5qqJGWTug+OpFkLQc91zYrMtMQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Essentially this decision is balancing legal risk
with inconveniencies, which is a tough trade-off to consider.
<div><br>
</div>
<div>It seems to me that the extra repository would be a
compromise that gets the balance right. Sure, there are some
drawbacks, but the legal story is quite straightforward and
clear. This is something where I'm tempted to trust the
lawyers and avoid experiments.</div>
<div><br>
</div>
<div>I would also like to congratulate Apple to make the
decision to contribute their LLVM changes back to the
community, and I think we should be welcoming and make this
straightforward for them.</div>
<div><br>
</div>
<div>Just my 2¢.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Jul 9, 2020 at 10:13
AM Roman Lebedev via llvm-dev <<a
href="mailto:llvm-dev@lists.llvm.org" target="_blank"
moz-do-not-send="true">llvm-dev@lists.llvm.org</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On
Thu, Jul 9, 2020 at 4:36 AM James Y Knight via llvm-dev<br>
<<a href="mailto:llvm-dev@lists.llvm.org" target="_blank"
moz-do-not-send="true">llvm-dev@lists.llvm.org</a>>
wrote:<br>
><br>
> As noted in the other thread, making a new repository
under the same user, which therefore must be unrelated to the
original, seems to have downsides as far as commit duplication
on github. Probably the downsides of that are non-critical
(and less bad than a bunch of email spam), but it's still
unfortunate.<br>
+1, i was asking about that in "[llvm-dev] Why is there a<br>
llvm/apple-llvm-project-staging ?"<br>
<a
href="https://lists.llvm.org/pipermail/llvm-dev/2020-June/142559.html"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/pipermail/llvm-dev/2020-June/142559.html</a><br>
<br>
Roman<br>
<br>
> It still very much feels to me that the best answer
should be to do none of the above, and rather to explicitly
contribute the desired changes without needing the technical
step of pushing the commits somewhere in <a
href="http://github.com/llvm/" rel="noreferrer"
target="_blank" moz-do-not-send="true">github.com/llvm/</a>.
Is that truly non-viable? The "plain" non-lawyer reading of
the license does not appear to privilege a "contribution"
which is done via "git push", vs a contribution done via
emailing a statement that you contribute git hash <X>,
found at <url> to the mailing list.<br>
><br>
><br>
> On Wed, Jul 8, 2020 at 8:00 PM Duncan Exon Smith via
llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org"
target="_blank" moz-do-not-send="true">llvm-dev@lists.llvm.org</a>>
wrote:<br>
>><br>
>> Okay, a separate repo called "llvm-project-staging"
(and a branch called "staging/apple") seems to be the
consensus. We'll move ahead with that!<br>
>><br>
>> On 2020-Jul-08, at 05:38, Mike Forster <<a
href="mailto:forster@google.com" target="_blank"
moz-do-not-send="true">forster@google.com</a>> wrote:<br>
>><br>
>> The downsides of an additional project are small. I
can see:<br>
>> 1) It's not possible to do pull requests from there,
because GitHub won't treat it as a fork.<br>
>> 2) It's still visible to people (<a
href="http://lists.llvm.org/pipermail/llvm-dev/2020-June/142559.html"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.llvm.org/pipermail/llvm-dev/2020-June/142559.html</a>)<br>
>><br>
>> In the end I don't have a strong opinion on whether
this is a branch or a repository, as long as we move ahead
soon.<br>
>><br>
>> On Thu, Jul 2, 2020 at 4:29 PM Johannes Doerfert via
llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org"
target="_blank" moz-do-not-send="true">llvm-dev@lists.llvm.org</a>>
wrote:<br>
>>><br>
>>><br>
>>> On 6/30/20 4:02 PM, Duncan Exon Smith via
llvm-dev wrote:<br>
>>> > Regardless, if a separate repo is preferred,
then a better name from our perspective would be
"llvm-project-staging" (dropping the "-apple" suffix). We
could push a "staging/apple" branch there.<br>
>>><br>
>>> +1 for a separate repo with a neutral name and
"company" branches.<br>
>>><br>
>>><br>
>>> * Unlikely we spam people<br>
>>><br>
>>> * Easy to understand from the github page<br>
>>><br>
>>> * Invisible to the existing users of
llvm-project/llvm<br>
>>><br>
>>> * Unlikely to confuse people that have or
download llvm (=accidental<br>
>>> build of staging/apple)<br>
>>><br>
>>><br>
>>> I haven't really seen a downside, though I might
have missed something.<br>
>>><br>
>>> _______________________________________________<br>
>>> LLVM Developers mailing list<br>
>>> <a href="mailto:llvm-dev@lists.llvm.org"
target="_blank" moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br>
>>> <a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> LLVM Developers mailing list<br>
>> <a href="mailto:llvm-dev@lists.llvm.org"
target="_blank" moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br>
>> <a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
><br>
> _______________________________________________<br>
> LLVM Developers mailing list<br>
> <a href="mailto:llvm-dev@lists.llvm.org" target="_blank"
moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br>
> <a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank"
moz-do-not-send="true">llvm-dev@lists.llvm.org</a><br>
<a
href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a>
</pre>
</blockquote>
</body>
</html>