www/licenses gpl-faq.html

[John Sullivan]

CVSROOT:        /web/www
Module name:    www
Changes by:     John Sullivan <johnsu01>        07/07/07 23:58:49

Modified files:
        licenses       : gpl-faq.html 

Log message:
        Seems like the right thing to do -- correct the date of the most recent 
change and refer to "Version 3 or later" instead of "Version 2 or later".

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.html?cvsroot=www&r1=1.102&r2=1.103

Patches:
Index: gpl-faq.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.html,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -b -r1.102 -r1.103
--- gpl-faq.html        29 Jun 2007 22:48:38 -0000      1.102
+++ gpl-faq.html        7 Jul 2007 23:58:33 -0000       1.103
@@ -263,8 +263,8 @@
     <li><a href="#GPLUSGovAdd" name="TOCGPLUSGovAdd">Can the US Government
     release improvements to a GPL-covered program?</a></li>
   
-    <li><a href="#VersionTwoOrLater" name="TOCVersionTwoOrLater">Why should
-    programs say "Version 2 of the GPL or any later version"?</a></li>
+    <li><a href="#VersionThreeOrLater" name="TOCVersionThreeOrLater">Why should
+    programs say "Version 3 of the GPL or any later version"?</a></li>
   
     <li><a href="#GPLOutput" name="TOCGPLOutput">Is there some way that I
     can GPL the output people get from use of my program?  For example, if
@@ -2157,14 +2157,14 @@
 convincing reasons.
 </p></dd>
 
-<dt><b><a href="#TOCVersionTwoOrLater" name="VersionTwoOrLater">Why
-should programs say "Version 2 of the GPL or any later version"?</a></b></dt>
+<dt><b><a href="#TOCVersionThreeOrLater" name="VersionThreeOrLater">Why
+should programs say "Version 3 of the GPL or any later version"?</a></b></dt>
 
 <dd>
-From time to time, at intervals of years, we change the GPL--sometimes
+From time to time, at intervals of years, we change the GPL&mdash;sometimes
 to clarify it, sometimes to permit certain kinds of use not previously
 permitted, and sometimes to tighten up a requirement.  (The last
-change was in 1991.)  Using this "indirect pointer" in each program
+two changes were in 2007 and 1991.)  Using this "indirect pointer" in each 
program
 makes it possible for us to change the distribution terms on the
 entire collection of GNU software, when we update the GPL.
 <p>
@@ -2173,23 +2173,23 @@
 would be a virtual impossibility.  In practice, the chance of having
 uniform distribution terms for GNU software would be nil.</p>
 <p>
-Suppose a program says "Version 2 of the GPL or any later version" and
+Suppose a program says "Version 3 of the GPL or any later version" and
 a new version of the GPL is released.  If the new GPL version gives
 additional permission, that permission will be available immediately
 to all the users of the program.  But if the new GPL version has a
 tighter requirement, it will not restrict use of the current version
-of the program, because it can still be used under GPL version 2.
-When a program says "Version 2 of the GPL or any later version", users
+of the program, because it can still be used under GPL version 3.
+When a program says "Version 3 of the GPL or any later version", users
 will always be permitted to use it, and even change it, according to
-the terms of GPL version 2--even after later versions of the GPL are
+the terms of GPL version 3&mdash;even after later versions of the GPL are
 available.</p>
 <p>
 If a tighter requirement in a new version of the GPL need not be
-obeyed for existing software, how is it useful?  Once GPL version 3 is
+obeyed for existing software, how is it useful?  Once GPL version 4 is
 available, the developers of most GPL-covered programs will release
-subsequent versions of their programs specifying "Version 3 of the GPL
+subsequent versions of their programs specifying "Version 4 of the GPL
 or any later version".  Then users will have to follow the tighter
-requirements in GPL version 3, for subsequent versions of the program.</p>
+requirements in GPL version 4, for subsequent versions of the program.</p>
 <p>
 However, developers are not obligated to do this; developers can
 continue allowing use of the previous version of the GPL, if that is
@@ -3036,7 +3036,7 @@
   <p>
     Updated:
     <!-- timestamp start -->
-    $Date: 2007/06/29 22:48:38 $
+    $Date: 2007/07/07 23:58:33 $
     <!-- timestamp end -->
   </p>
 </div>