GNU Autoconf Archive branch master updated. v2015.02.04-15-g3c61f64

[E-mail notifications for the Autoconf Archive git repository.]

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 Autoconf Archive".

The branch, master has been updated
       via  3c61f6419a4b40c6d4ad68c7b376d00dde274e82 (commit)
      from  3aa0e8c6f10c648921d23853c284e3d75bdd082c (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 3c61f6419a4b40c6d4ad68c7b376d00dde274e82
Author: Peter Johansson <address@hidden>
Date:   Wed Feb 11 14:26:33 2015 +0100

    AX_APPEND_FLAG: fix regression
    
    AX_APPEND_FLAG has changed behaviour compared to earlier versions: it
    adds the FLAG also when the variable contains FLAG. I traced down the
    altered behaviour to the two lines
    
     [case " AS_VAR_GET(FLAGS) " in
        *" $1 "*)
    
    which have changed to
    
      AS_CASE([AS_VAR_GET(FLAGS)],
        ["* $1 *|*$1"]
    
    besides that AS_CASE is used (which is good imho) the pattern has
    changed and the space around FLAGS in the first argument of AS_CASE has
    gone. This means that e.g. if FLAGS is "alpha beta gamma" that will not
    match the pattern "* $1 *|*$1" for $1 being any of 'alpha', 'beta', or
    'gamma'. I think that is unexpected behaviour.
    
    This patch restores the original semantics.
    
    For further details can be found at:
    
      
http://lists.gnu.org/archive/html/autoconf-archive-maintainers/2015-02/msg00000.html

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

Summary of changes:
 NEWS                 |    2 ++
 m4/ax_append_flag.m4 |    6 +++---
 2 files changed, 5 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
GNU Autoconf Archive