X-Git-Url: http://plrg.eecs.uci.edu/git/?a=blobdiff_plain;f=docs%2FDeveloperPolicy.html;h=19aef36984f98b5909980920a65077e353a2c174;hb=d5e2d40693af9838d6a6504959536ed81c185540;hp=e5e7b12b5f8703a6db55be9bf21af95eee1e8d34;hpb=88e37ae36652546c8e409cab69a1777af63cf095;p=oota-llvm.git

diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index e5e7b12b5f8..19aef36984f 100644
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -447,10 +447,10 @@ Changes</a></div>
   with the GPL, and must be releasable under the terms of the GPL.  This implies
   that <b>any code linked into llvm-gcc and distributed to others may be subject
   to the viral aspects of the GPL</b> (for example, a proprietary code generator
-  linked into llvm-gcc must be made available under
-  the GPL).  This is not a problem for the main LLVM
-  distribution (which is already licensed under a more liberal license), but may
-  be a problem if you intend to base commercial development on llvm-gcc without
+  linked into llvm-gcc must be made available under the GPL).  This is not a
+  problem for code already distributed under a more liberal license (like the
+  UIUC license), and does not affect code generated by llvm-gcc.  It may be a
+  problem if you intend to base commercial development on llvm-gcc without
   redistributing your source code.</p>
   
   <p>We have no plans to change the license of LLVM.  If you have questions