gnustandards-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnustandards ChangeLog maintain.texi


From: Karl Berry
Subject: gnustandards ChangeLog maintain.texi
Date: Wed, 21 Mar 2012 15:04:56 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       12/03/21 15:04:56

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        using ftp.gnu.org is strongly recommended but not absolutely required

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.156&r2=1.157
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.215&r2=1.216

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.156
retrieving revision 1.157
diff -u -b -r1.156 -r1.157
--- ChangeLog   11 Mar 2012 18:17:39 -0000      1.156
+++ ChangeLog   21 Mar 2012 15:04:55 -0000      1.157
@@ -1,3 +1,9 @@
+2012-03-21  Karl Berry  <address@hidden>
+
+       * maintain.texi (Distribution on ftp.gnu.org): clarify that
+       using ftp.gnu.org is strongly recommended, though not
+       absolutely required.
+
 2012-03-11  Karl Berry  <address@hidden>
 
        * maintain.texi (Announcements): missed @indicateurl for

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.215
retrieving revision 1.216
diff -u -b -r1.215 -r1.216
--- maintain.texi       11 Mar 2012 18:17:39 -0000      1.215
+++ maintain.texi       21 Mar 2012 15:04:56 -0000      1.216
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate March 11, 2012
address@hidden lastupdate March 20, 2012
 @c %**end of header
 
 @dircategory GNU organization
@@ -1361,18 +1361,21 @@
 It's wise to test your patch by applying it to a copy of the old
 version, and checking that the result exactly matches the new version.
 
+
 @node Distribution on ftp.gnu.org
 @section Distribution on @code{ftp.gnu.org}
 @cindex GNU ftp site
 @cindex @code{ftp.gnu.org}, the GNU release site
 
-GNU packages are distributed through the directory @file{/gnu} on
address@hidden, via both HTTP and FTP.  Each package should have a
-subdirectory named after the package, and all the distribution files
-for the package should go in that subdirectory.
+We strongly recommend using @code{ftp.gnu.org} to distribute official
+releases.  If you want to also distribute the package from a site of
+your own, that is fine.  To use some other site instead of
address@hidden is acceptable, provided it allows connections from
+anyone anywhere.
+
address@hidden FTP Uploads}, for the procedural details of putting
+new versions on @code{ftp.gnu.org}.
 
address@hidden FTP Uploads}, for procedural details of putting new
-versions on @code{ftp.gnu.org}.
 
 @node Test Releases
 @section Test Releases
@@ -1387,8 +1390,8 @@
 a suitable GNU mailing list/newsgroup to recruit them.)
 
 We normally use the server @code{alpha.gnu.org} for pretests and
-prerelease versions.  @xref{Automated FTP Uploads}, for procedural details
-of putting new versions on @code{alpha.gnu.org}.
+prerelease versions.  @xref{Automated FTP Uploads}, for the procedural
+details of putting new versions on @code{alpha.gnu.org}.
 
 Once a program gets to be widely used and people expect it to work
 solidly, it is a good idea to do pretest releases before each ``real''



reply via email to

[Prev in Thread] Current Thread [Next in Thread]