trans-coord/gnun home.shtml licenses/gpl-faq.html

[Yavor Doganov]

CVSROOT:        /sources/trans-coord
Module name:    trans-coord
Changes by:     Yavor Doganov <yavor>   08/04/11 20:10:07

Modified files:
        gnun           : home.shtml 
        gnun/licenses  : gpl-faq.html 

Log message:
        Automatic sync from the master www repository.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/home.shtml?cvsroot=trans-coord&r1=1.17&r2=1.18
http://cvs.savannah.gnu.org/viewcvs/trans-coord/gnun/licenses/gpl-faq.html?cvsroot=trans-coord&r1=1.3&r2=1.4

Patches:
Index: home.shtml
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/home.shtml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- home.shtml  10 Apr 2008 20:10:05 -0000      1.17
+++ home.shtml  11 Apr 2008 20:10:06 -0000      1.18
@@ -108,7 +108,9 @@
 <a href="/doc/book13.html">Free Software, Free Society</a>.
 </p>
 
-<p>The FSF also has 'sister' organisations in <a 
href="http://www.fsfeurope.org";>Europe</a>, <a 
href="http://www.fsfla.org/";>Latin America</a> and <a 
href="http://fsf.org.in/";>India</a></p>
+<p>The FSF also has sister organizations
+in <a href="http://www.fsfeurope.org";>Europe</a>, <a 
href="http://www.fsfla.org/";>Latin
+America</a> and <a href="http://fsf.org.in/";>India</a>.</p>
 
 <!--
    Keep link lines at 72 characters or lynx will break them poorly.
@@ -129,9 +131,10 @@
 
   <p>A monthly update on GNU and the Free Software Foundation</p>
 
-  <form action="http://lists.gnu.org/mailman/subscribe/info-fsf"; method="post">
+  <form action="http://lists.gnu.org/mailman/subscribe/info-fsf";
+       method="post">
     <p><input type="text" id="frmEmail" name="email" size="35" maxlength="80" 
value="address@hidden" onfocus="this.value=''" /> &nbsp; <input type="submit" 
value="Subscribe me" /></p>
-
+  </form>
 </div>
 
   <h3>More information</h3>
@@ -285,7 +288,7 @@
 
 <p>Last Updated:
    <!-- timestamp start -->
-   $Date: 2008/04/10 20:10:05 $
+   $Date: 2008/04/11 20:10:06 $
    <!-- timestamp end -->
 </p>
   

Index: licenses/gpl-faq.html
===================================================================
RCS file: /sources/trans-coord/trans-coord/gnun/licenses/gpl-faq.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- licenses/gpl-faq.html       10 Apr 2008 20:10:06 -0000      1.3
+++ licenses/gpl-faq.html       11 Apr 2008 20:10:07 -0000      1.4
@@ -327,9 +327,9 @@
     if I give users the diffs from the &ldquo;standard&rdquo; version along
     with the binaries?</a></li>
   
-    <li><a href="#AnonFTPAndSendSources">I want to make binaries
-    available for anonymous FTP, but send sources only to people who
-    order them.</a></li>
+    <li><a href="#AnonFTPAndSendSources">Can I make binaries
+    available on a network server, but send sources only to people who
+    order them?</a></li>
 
     <li><a href="#HowCanIMakeSureEachDownloadGetsSource">How can I make
     sure each user who downloads the binaries also gets the
@@ -1986,23 +1986,24 @@
 the binaries.
 </p></dd>
 
-<dt><b><a
-  name="AnonFTPAndSendSources">I want to make binaries available for
-  anonymous FTP, but send sources only to people who order them.</a></b></dt>
-
-<dd><p>If you want to distribute binaries by anonymous FTP, you have to
-distribute sources along with them.  This should not be hard.  If you can
-find a site to distribute your program, you can surely find one that has
-room for the sources.</p>
+<dt><b><a name="AnonFTPAndSendSources">Can I make binaries available
+  on a network server, but send sources only to people who order
+  them?</a></b></dt>
+
+<dd><p>If you make object code available on a network server, you have
+    to provide the Corresponding Source on a network server as well.
+    The easiest way to do this would be to publish them on the same
+    server, but if you'd like, you can alternatively provide
+    instructions for getting the source from another server, or even a
+    <a href="#SourceInCVS">version control system</a>.  No matter what
+    you do, the source should be just as easy to access as the object
+    code, though.  This is all specified in section 6(d) of GPLv3.</p>
 
 <p>The sources you provide must correspond exactly to the binaries.
 In particular, you must make sure they are for the same version of
 the program&mdash;not an older version and not a newer version.</p>
 
-<p>You can make the sources and binaries available on different machines,
-provided they are equally easy to get to, and provided that you have
-information next to the binaries saying where to find the sources.
-</p></dd>
+</dd>
 
 <dt><b><a
   name="HowCanIMakeSureEachDownloadGetsSource">How can I make sure each
@@ -2919,10 +2920,11 @@
 <p>This is acceptable as long as the source checkout process does not
 become burdensome or otherwise restrictive.  Anybody who can download
 your object code should also be able to check out source from your
-VCS, using a publicly available free software client.  Users should be
-provided with clear and convenient instructions for how to get the
-source for the exact object code they downloaded&mdash;they may not
-necessarily want the latest development code, after all.</p>
+version control system, using a publicly available free software
+client.  Users should be provided with clear and convenient
+instructions for how to get the source for the exact object code they
+downloaded&mdash;they may not necessarily want the latest development
+code, after all.</p>
 </dd>
 
 <dt><b><a name="RemoteAttestation">Can
@@ -3306,7 +3308,7 @@
   <p>
     Updated:
     <!-- timestamp start -->
-    $Date: 2008/04/10 20:10:06 $
+    $Date: 2008/04/11 20:10:07 $
     <!-- timestamp end -->
   </p>
 </div>