@@ -21,20 +21,15 @@ progress. Any given snapshot may generate incorrect code or even fail to
build.</p>
<p>If you plan on downloading and using snapshots, we highly recommend you
-subscribe to the GCC mailing lists. See <a href="lists.html">
-mailing lists</a> on the main GCC page for instructions on how to subscribe.</p>
+subscribe to the GCC <a href="lists.html">mailing lists</a>.</p>
<p>When using the diff files to update from older snapshots to newer snapshots,
make sure to use "-E" and "-p" arguments to patch so that empty files are
-deleted and full pathnames are provided to patch. If your version of
-patch does not support "-E", you'll need to get a newer version. Also note
-that you may need autoconf, autoheader and various other programs if you use
-diff files to update from one snapshot to the next.</p>
+deleted and full pathnames are provided to patch.</p>
<p><code>contrib/gcc_update</code> can be used to apply diffs between
successive snapshot versions and preserve relations between generated
-files so that autoconf et al aren't needed. This is documented in
-comments in contrib/gcc_update.</p>
+files so that autoconf et al aren't needed.</p>
<p>The program <code>sha512sum</code> — which is included with the
<a href="https://www.gnu.org/software/coreutils/">GNU Coreutils</a>