validation fixes

[oota-llvm.git] / docs / DeveloperPolicy.html

diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index e9cd4ded7671acf48602d0d5c6e912497ed82003..85b8aab2c1b23099eab5583623cb259c317dcf5e 100644 (file)
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -162,7 +162,7 @@
     bug being fixed or feature being implemented is in the llvm-gcc C++
     front-end, in which case it must be written in C++).</li>
     <li>Test cases, especially for regressions, should be reduced as much as 
-    possible, by <a href="CommandGuide/html/bugpoint.html">bugpoint</a> or
+    possible, by <a href="Bugpoint.html">bugpoint</a> or
     manually. It is unacceptable 
     to place an entire failing program into <tt>llvm/test</tt> as this creates
     a <i>time-to-test</i> burden on all developers. Please keep them short.</li>
@@ -254,7 +254,7 @@ quality patches.  If you would like commit access, please send an email to the
 <p>In any case, your changes are still subject to <a href="#reviews">code
 review</a> (either before or after they are committed, depending on the nature
 of the change).  You are encouraged to review other peoples' patches as well,
-but your aren't required to.</p>
+but you aren't required to.</p>
   
 </div>
 
@@ -442,15 +442,15 @@ Changes</a></div>
   read the <a href="http://www.opensource.org/licenses/UoI-NCSA.php">License</a>
   if further clarification is needed.</p>
   
-  <p>Note that the LLVM Project does distribute some code that includes GPL
-  software (notably, llvm-gcc which is based on the GCC GPL source base).
-  This means that anything "linked" into to llvm-gcc must itself be compatible
+  <p>Note that the LLVM Project does distribute llvm-gcc, <b>which is GPL.</b>
+  This means that anything "linked" into llvm-gcc must itself be compatible
   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>.  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
+  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 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