<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:clattner@nondot.org" title="Chris Lattner <clattner@nondot.org>"> <span class="fn">Chris Lattner</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Missing LLVM NOTICE file is making redistributing LLVM difficult"
href="https://bugs.llvm.org/show_bug.cgi?id=46201">bug 46201</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Missing LLVM NOTICE file is making redistributing LLVM difficult"
href="https://bugs.llvm.org/show_bug.cgi?id=46201#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Missing LLVM NOTICE file is making redistributing LLVM difficult"
href="https://bugs.llvm.org/show_bug.cgi?id=46201">bug 46201</a>
from <span class="vcard"><a class="email" href="mailto:clattner@nondot.org" title="Chris Lattner <clattner@nondot.org>"> <span class="fn">Chris Lattner</span></a>
</span></b>
<pre>Hi Jukka,
We discussed this with the LLVM Foundation board. While we think there is high
utility to providing such a NOTICES file, we don’t know of a way to keep it up
to date, and don’t want to be providing incorrect information for such an
important topic.
That said, the llvm/LICENSE.TXT checked into the code has this information
about how to identify third party licenses in the code base. I hope this is
enough to help with your analysis.
==============================================================================
Software from third parties included in the LLVM Project:
==============================================================================
The LLVM Project contains third party software which is under different license
terms. All such code will be identified clearly using at least one of two
mechanisms:
1) It will be in a separate directory tree with its own `LICENSE.txt` or
`LICENSE` file at the top containing the specific license and restrictions
which apply to that software, or
2) It will contain specific license and restriction terms at the top of every
file.
Thanks!
-Chris</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>