From: Peter Rosin <peda@lysator.liu.se>
Date: Sat, 17 Mar 2012 19:13:53 +0000 (+0100)
Subject: bootstrap: delete unneeded README-release patch
X-Git-Tag: v2.4.2.418~190
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=11cd425e7d47111956381dba28f8c1b34e14653f;p=thirdparty%2Flibtool.git

bootstrap: delete unneeded README-release patch

* gl/top/README-release.diff: Delete.
---

diff --git a/gl/top/README-release.diff b/gl/top/README-release.diff
deleted file mode 100644
index 4cc43f3a5..000000000
--- a/gl/top/README-release.diff
+++ /dev/null
@@ -1,38 +0,0 @@
---- gnulib/top/README-release	2011-12-24 08:28:59.000000000 +0700
-+++ gl/top/README-release	2011-12-24 09:01:01.000000000 +0700
-@@ -1,5 +1,9 @@
- Here are most of the steps we (maintainers) follow when making a release.
- 
-+* If you don't yet have gnu ftp upload rights, read this:
-+
-+    https://www.gnu.org/prep/maintain/html_node/Automated-Upload-Registration.html#Automated-Upload-Registration
-+
- * start from a clean, up-to-date git directory.
- 
-     make -k maintainer-clean || { ./configure && make maintainer-clean; }
-@@ -18,12 +22,24 @@
- 
-     http://hydra.nixos.org/jobset/gnu/@PACKAGE@-master
- 
--* Run "./bootstrap && ./configure".  This downloads any new translations.
-+* Double check that serial number updates in public m4 files weren't
-+  forgotten since last release (they should be updated in git along with
-+  commits that require it so that users can work with git snapshots).
-+
-+* Update the LTDL_VERSION_INFO in libltdl/Makefile.inc for changes since
-+  the last release.
-+
-+* Run "./bootstrap && ./configure".
- 
- * Pre-release testing:
-   Ensure that "make check syntax-check" succeeds.
- 
- * Run "make distcheck"
-+  and `make distcheck DISTCHECK_CONFIGURE_FLAGS=--disable-ltdl-install'
-+  and `make distcheck DISTCHECK_CONFIGURE_FLAGS=--program-prefix=g'
-+  and `make distcheck DISTCHECK_CONFIGURE_FLAGS=--disable-shared'
-+  and `make distcheck CC=g++'
-+  If there are any problems, fix them and start again.
- 
- * Set the date, version number, and release type [stable/alpha/beta] on
-   line 3 of NEWS, commit that, and tag the release by running e.g.,