From b3c1f16f0a332b44502f6cca7ca643a59c6d924f Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sun, 31 Dec 2017 16:26:12 -0800 Subject: [PATCH] autoupdate --- doc/maintain.texi | 2 +- doc/standards.texi | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/maintain.texi b/doc/maintain.texi index e1f82de714..f75ec9801a 100644 --- a/doc/maintain.texi +++ b/doc/maintain.texi @@ -1828,7 +1828,7 @@ comment: creates per-version subdirectory as needed @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 diff --git a/doc/standards.texi b/doc/standards.texi index baf653e291..15850147bb 100644 --- a/doc/standards.texi +++ b/doc/standards.texi @@ -3849,7 +3849,7 @@ with the FSF about the individual case. @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 -- 2.39.5