autoupdate

diff --git a/doc/maintain.texi b/doc/maintain.texi
index c1184a79664d6776d6769e6cb5562c5e7af091a3..9eada85bae1f4e9b754ba0bab8c6055ede110438 100644 (file)
--- a/doc/maintain.texi
+++ b/doc/maintain.texi
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
-@set lastupdate November 14, 2010
+@set lastupdate November 22, 2010
 @c %**end of header
 
 @dircategory GNU organization
@@ -1345,7 +1345,7 @@ good to also send your key to the GPG public key server: @code{gpg
 --keyserver keys.gnupg.net --send-keys @var{keyid}}, where @var{keyid}
 is the eight hex digits reported by @code{gpg --list-public-keys} on
 the @code{pub} line before the date.  For full information about GPG,
-see @url{http://www.gnu.org/software/gpg})
+see @url{http://www.gnu.org/software/gpg}.
 
 @item
 Compose a message with the following items in some @var{msgfile}.
@@ -2083,24 +2083,30 @@ on www.gnu.org for more information on how to contribute.
 
 As a maintainer, you might want to accept donations for your work,
 especially if you pay for any of your own hosting/development
-infrastructure.  Following is some text you can adapt for your
-package's web site, @file{README}, or wherever you find it useful:
+infrastructure.  Following is some text you can adapt to your own
+situation, and use on your package's web site, @file{README}, or
+in wherever way you find it useful:
 
 @smallexample
 We appreciate contributions of any size -- donations enable us to spend
 more time working on the project, and help cover our infrastructure
 expenses.
 
-If you'd like to make a small donation, please visit @var{url} and do
+If you'd like to make a small donation, please visit @var{url1} and do
 it through @var{payment-service}.  Since our project isn't a
 tax-exempt organization, we can't offer you a tax deduction, but for
-all donations over @var{amount}, we'd be happy to recognize your
-contribution on @var{another-url}.
+all donations over @var{amount1}, we'd be happy to recognize your
+contribution on @var{url2}.
 
-If you can make a donation large enough to entirely fund a substantial
-change, such as $1000, then we could discuss with you what change we
-should do with your funds, and we could give you a certain amount of
-specific help in exchange.  Write to us about this at @var{address}.
+We are also happy to consider making particular improvements or
+changes, or giving specific technical assistance, in return for a
+substantial donation over @var{amount2}.  If you would like to discuss
+this possibility, write to us at @var{address}.
+
+Another possibility is to pay a software maintenance fee.  Again,
+write to us about this at @var{address} to discuss how much you want
+to pay and how much maintenance we can offer in return.  If you pay
+more than @var{amount1}, we can give you a document for your records.
 
 Thanks for your support!
 @end smallexample
@@ -2109,6 +2115,10 @@ We don't recommend any specific payment service.  However, GNU
 developers should not use a service that requires them to sign a
 proprietary software license, such as Google's payment service.
 
+Of course, it is also good to encourage people to join or contribute
+to the FSF (@url{http://www.fsf.org}), either instead of or as well as
+package-specific donations.
+
 
 @node Free Software Directory
 @chapter Free Software Directory

diff --git a/doc/make-stds.texi b/doc/make-stds.texi
index 6c83b5d58fe02e52d9617ae22bdd907af57e78f8..cdcbb682ab6c77e0267c3f9c350c9bab71157dd8 100644 (file)
--- a/doc/make-stds.texi
+++ b/doc/make-stds.texi
@@ -715,8 +715,9 @@ documentation format) files should be made only when explicitly asked
 for.
 
 By default, the Make rules should compile and link with @samp{-g}, so
-that executable programs have debugging symbols.  Users who don't mind
-being helpless can strip the executables later if they wish.
+that executable programs have debugging symbols.  Otherwise, you are
+essentially helpless in the face of a crash, and it is often far from
+easy to reproduce with a fresh build.
 
 @item install
 Compile the program and copy the executables, libraries, and so on to
@@ -724,8 +725,11 @@ the file names where they should reside for actual use.  If there is a
 simple test to verify that a program is properly installed, this target
 should run that test.
 
-Do not strip executables when installing them.  Devil-may-care users can
-use the @code{install-strip} target to do that.
+Do not strip executables when installing them.  This helps eventual
+debugging that may be needed later, and nowadays disk space is cheap
+and dynamic loaders typically ensure debug sections are not loaded during
+normal execution.  Users that need stripped binaries may invoke the
+@code{install-strip} target to do that.
 
 If possible, write the @code{install} target rule so that it does not
 modify anything in the directory where the program was built, provided
@@ -837,10 +841,7 @@ the program has no bugs.  However, it can be reasonable to install a
 stripped executable for actual execution while saving the unstripped
 executable elsewhere in case there is a bug.
 
-@comment The gratuitous blank line here is to make the table look better
-@comment in the printed Make manual.  Please leave it in.
 @item clean
-
 Delete all files in the current directory that are normally created by
 building the program.  Also delete files in other directories if they
 are created by this makefile.  However, don't delete the files that