changeset 39197:1a2841157ac5

autoupdate
author Paul Eggert <eggert@cs.ucla.edu>
date Sun, 31 Dec 2017 16:26:12 -0800
parents c9c758400c81
children b40116976b39
files doc/maintain.texi doc/standards.texi
diffstat 2 files changed, 2 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/doc/maintain.texi	Sun Dec 31 08:53:16 2017 -0800
+++ b/doc/maintain.texi	Sun Dec 31 16:26:12 2017 -0800
@@ -1828,7 +1828,7 @@
 @noindent
 would put the tar file in the @file{foo-1.0/} subdirectory of the
 package @code{foo}, thus ending up at
-@indicateurl{ftp.gnu.org:gnu/foo/foo-1.0/foo-1.0.tar.gz}.
+@indicateurl{https://ftp.gnu.org/pub/gnu/foo/foo-1.0/foo-1.0.tar.gz}.
 
 However, to keep things simpler for users, we recommend not using
 subdirectories, unless perhaps each release of your package consists
--- a/doc/standards.texi	Sun Dec 31 08:53:16 2017 -0800
+++ b/doc/standards.texi	Sun Dec 31 16:26:12 2017 -0800
@@ -3849,7 +3849,7 @@
 @cindex releasing
 
 Making a release is more than just bundling up your source files in a
-tar file and putting it up for FTP.  You should set up your software so
+tar file and publishing it.  You should set up your software so
 that it can be configured to run on a variety of systems.  Your Makefile
 should conform to the GNU standards described below, and your directory
 layout should also conform to the standards discussed below.  Doing so