Ever since commit f1cf390 (1.4.14 release), we no longer create diff files as part of the release process. These days, it is assumed that it is easier to download a fresh tarball rather than to try and use a diff file to patch an older tarball.
Signed-off-by: Eric Blake <[email protected]> (cherry picked from commit c8a4b7c32db3a6d8d5dc7a9997df2c80ac95b030) --- HACKING | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/HACKING b/HACKING index 08a949a..83990e1 100644 --- a/HACKING +++ b/HACKING @@ -277,9 +277,6 @@ yyyy-mm-dd Name of Author <email@address> (tiny change) * Make sure you have rsync installed. -* Make sure you have a copy of the previous release tarball in the build - directory. - * Make sure you have GNU make installed. * Make sure you have an up-to-date version of help2man installed. @@ -317,9 +314,8 @@ yyyy-mm-dd Name of Author <email@address> (tiny change) * Run `make distcheck'. If there are any problems, fix them, then run `git tag -d v<version>' and start again from the `git commit' step. -* Run `make <target>', with target set to `stable, `alpha', or `beta' as - appropriate. This will run various additional checks and create diff - files from the previous version. +* Run `make <target>', with target set to `stable', `alpha', or `beta' + as appropriate. This will run various additional checks. * Run './build-aux/gnupload --to [dest].gnu.org:m4 [files]' to create detached gpg signature and clear signed directive files, and upload -- 2.9.3 _______________________________________________ M4-patches mailing list [email protected] https://lists.gnu.org/mailman/listinfo/m4-patches
