From 7d8012b602ee3456072bf61a10574d8753990eac Mon Sep 17 00:00:00 2001
From: Chris Lattner <sabre@nondot.org>
Date: Thu, 22 Feb 2007 06:33:23 +0000
Subject: [PATCH] clarify llvm-gcc GPL issue

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34486 91177308-0d34-0410-b5e6-96231b3b80d8
---
 docs/DeveloperPolicy.html | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index 871cc724282..e5e7b12b5f8 100644
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -442,13 +442,13 @@ 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).
+  <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
+  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
   redistributing your source code.</p>
-- 
2.34.1