FYI: small HACKING update

[Ralf Wildenhues]

I fixed a couple of typos in HACKING.  Also, CVS_RSH is not needed for
pserver.  Also, I added a note to look in README for how to report
verbose test failures.

        * HACKING: Update.

Index: HACKING
===================================================================
RCS file: /cvsroot/libtool/libtool/HACKING,v
retrieving revision 1.32
diff -u -r1.32 HACKING
--- HACKING     28 Jan 2007 12:43:36 -0000      1.32
+++ HACKING     17 Feb 2007 09:56:16 -0000
@@ -493,7 +493,7 @@
 You should download the signature named after any tarball you download,
 and then verify its integrity with, for example:
 
-  gpg --verify address@hidden
+  gpg --verify address@hidden@.tar.gz.sig
 
 Here are the MD5 and SHA1 checksums:
 
@@ -512,12 +512,11 @@
 but is useable with @COMPATIBLE_AUTOTOOL_VERSIONS@ in your own
 projects.
 
-Alternatively, you can fetch the unbootstrapped sourcecode from
-anonymous cvs by using the following commands:
+Alternatively, you can fetch the unbootstrapped source code from
+anonymous cvs by using the following command:
 
-  $ export CVS_RSH=ssh
   $ cvs -z3 -d :pserver:address@hidden:/sources/libtool \
-  co -r @CVS_RELEASE_TAG@ libtool
+    co -r @CVS_RELEASE_TAG@ libtool
 
 You will then need to have recent (possibly as yet unreleased) versions
 of Automake and Autoconf installed to bootstrap the checked out
@@ -529,6 +528,7 @@
 
 Please report bugs to <address@hidden>, along with the verbose
 output of any failed test groups, and the output from `./libtool --config.'
+The README file explains how to capture the verbose test output.
 
 
 
@@ -580,7 +580,7 @@
 You should download the signature named after any tarball you download,
 and then verify its integrity with, for example:
 
-  gpg --verify address@hidden
+  gpg --verify address@hidden@.tar.gz.sig
 
 Here are the MD5 and SHA1 checksums:
 
@@ -597,13 +597,12 @@
 but is useable with @COMPATIBLE_AUTOTOOL_VERSIONS@ in your own
 projects.
 
-Alternatively, you can fetch the unbootstrapped sourcecode from
-anonymous cvs by using the following commands (just hit return when
+Alternatively, you can fetch the unbootstrapped source code from
+anonymous cvs by using the following command (just hit return when
 you are prompted for the password):
 
-  $ export CVS_RSH=ssh
   $ cvs -z3 -d :pserver:address@hidden:/sources/libtool \
-  co -r @CVS_RELEASE_TAG@ libtool
+    co -r @CVS_RELEASE_TAG@ libtool
 
 You will then need to have the latest release versions of Automake
 (@AUTOMAKE_VERSION@) and Autoconf (@AUTOCONF_VERSION@) installed to
@@ -611,6 +610,7 @@
 
 Please report bugs to <address@hidden>, along with the verbose
 output of any failed test groups, and the output from `./libtool --config.'
+The README file explains how to capture the verbose test output.
 
 
 --