[SCM] GNU Libtool branch, master, updated. v2.4.3-32-g8c2154f

2014-11-18 Thread Gary V. Vaughan
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  8c2154fb4e80967b50b98c7327ff1465d3315f3f (commit)
  from  5ecee55e0fa9478e2046f1d67f4111b5bd6ce227 (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 8c2154fb4e80967b50b98c7327ff1465d3315f3f
Author: Vincent Lefevre vinc...@vinc17.net
Date:   Tue Nov 18 16:14:35 2014 +

NEWS: Fix an ancient spelling mistake,

* NEWS: s/propogate/progagote.
* cfg.mk (old_NEWS_hash): Update.

Signed-off-by: Gary V. Vaughan g...@gnu.org

---

Summary of changes:
 NEWS   |2 +-
 cfg.mk |2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/NEWS b/NEWS
index 9bff558..75da6ea 100644
--- a/NEWS
+++ b/NEWS
@@ -604,7 +604,7 @@ New in 1.9b: 2004-08-29; CVS version 1.5a, Libtool team:
 * If you configure libtool with --disable-shared (or if libtool does not
   support shared libraries on your platform) trying to build a library using
   '-shared' is a fatal error.
-* New link mode option '-weak' tells libtool when not to propogate dependency
+* New link mode option '-weak' tells libtool when not to propagate dependency
   libraries from dlpreopened modules.
 * libtoolize installs libtool.m4, (ltdl.m4 if used,) and various supporting
   m4 definitions to AC_CONFIG_MACRO_DIR.
diff --git a/cfg.mk b/cfg.mk
index 7c73540..497e53e 100644
--- a/cfg.mk
+++ b/cfg.mk
@@ -24,7 +24,7 @@
 update-copyright-env := UPDATE_COPYRIGHT_FORCE=1 
UPDATE_COPYRIGHT_USE_INTERVALS=1
 
 # Set format of NEWS
-old_NEWS_hash := aff57203fce23f130c7c8e9652489229
+old_NEWS_hash := e524180c3db06628ad97e3fcb35f6a4b
 
 manual_title = Portable Dynamic Shared Object Management
 


hooks/post-receive
-- 
GNU Libtool



Re: [SCM] GNU Libtool branch, master, updated. v2.4.3-32-g8c2154f

2014-11-18 Thread Eric Blake
On 11/18/2014 09:15 AM, Gary V. Vaughan wrote:
 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  8c2154fb4e80967b50b98c7327ff1465d3315f3f (commit)
   from  5ecee55e0fa9478e2046f1d67f4111b5bd6ce227 (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 8c2154fb4e80967b50b98c7327ff1465d3315f3f
 Author: Vincent Lefevre vinc...@vinc17.net
 Date:   Tue Nov 18 16:14:35 2014 +
 
 NEWS: Fix an ancient spelling mistake,
 
 * NEWS: s/propogate/progagote.

Not quite: s/progagote/propagate/ in the changelog entry (so now you
need a patch to build/git-log-fix...)

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature


Re: [SCM] GNU Libtool branch, master, updated. v2.4.3-32-g8c2154f

2014-11-18 Thread Gary V. Vaughan

 On Nov 18, 2014, at 4:49 PM, Eric Blake ebl...@redhat.com wrote:
 
 On 11/18/2014 09:15 AM, Gary V. Vaughan wrote:
 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  8c2154fb4e80967b50b98c7327ff1465d3315f3f (commit)
  from  5ecee55e0fa9478e2046f1d67f4111b5bd6ce227 (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 8c2154fb4e80967b50b98c7327ff1465d3315f3f
 Author: Vincent Lefevre vinc...@vinc17.net
 Date:   Tue Nov 18 16:14:35 2014 +
 
NEWS: Fix an ancient spelling mistake,
 
* NEWS: s/propogate/progagote.
 
 Not quite: s/progagote/propagate/ in the changelog entry (so now you
 need a patch to build/git-log-fix...)

I hate you! :-p