[SCM] GNU Libtool branch, master, updated. v2.2.8-9-gb188543

[Ralf Wildenhues]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Libtool".

The branch, master has been updated
       via  b188543381ff1b0815e7e301d2f40170868abe82 (commit)
      from  b33d82439af7213436aa02188d475fcf24b130d0 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit b188543381ff1b0815e7e301d2f40170868abe82
Author: Ralf Wildenhues <address@hidden>
Date:   Sun Jun 6 13:21:39 2010 +0200

    Rewrite manual intro to be gender-neutral.
    
    * doc/libtool.texi (Introduction): Use gender-neutral
    formulation when addressing developers.
    
    Signed-off-by: Ralf Wildenhues <address@hidden>

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog        |    6 ++++++
 doc/libtool.texi |   12 ++++++------
 2 files changed, 12 insertions(+), 6 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 6c397c9..b79b004 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2010-06-06  Ralf Wildenhues  <address@hidden>
+
+       Rewrite manual intro to be gender-neutral.
+       * doc/libtool.texi (Introduction): Use gender-neutral
+       formulation when addressing developers.
+
 2010-06-05  Gary V. Vaughan  <address@hidden>
 
        Update and simplify all m4sh scripts to use latest getopt.m4sh.
diff --git a/doc/libtool.texi b/doc/libtool.texi
index bbc22f4..051aec3 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -230,13 +230,13 @@ Platform quirks
 @node Introduction
 @chapter Introduction
 
-In the past, if a source code package developer wanted to take advantage
-of the power of shared libraries, he needed to write custom support code
-for each platform on which his package ran.  He also had to design a
-configuration interface so that the package installer could choose what
-sort of libraries were built.
+In the past, if you were a source code package developer and wanted to
+take advantage of the power of shared libraries, you needed to write
+custom support code for each platform on which your package ran.  You
+also had to design a configuration interface so that the package
+installer could choose what sort of libraries were built.
 
-GNU Libtool simplifies the developer's job by encapsulating both the
+GNU Libtool simplifies your job by encapsulating both the
 platform-specific dependencies, and the user interface, in a single
 script.  GNU Libtool is designed so that the complete functionality of
 each host type is available via a generic interface, but nasty quirks


hooks/post-receive
-- 
GNU Libtool