[SCM] GNU libidn branch, master, updated. libidn-1-21-5-gfed6dbd

[Simon Josefsson]

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 libidn".

http://git.savannah.gnu.org/cgit/libidn.git/commit/?id=fed6dbd707975dbcc9e7e7817a377f058eef181d

The branch, master has been updated
       via  fed6dbd707975dbcc9e7e7817a377f058eef181d (commit)
      from  8db3c99d6b43bac564b86b65fa9ea5fdc7682577 (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 fed6dbd707975dbcc9e7e7817a377f058eef181d
Author: Simon Josefsson <address@hidden>
Date:   Mon Apr 25 22:00:02 2011 +0200

    Document --disable-valgrind-tests.
    
    Suggested by Guido Trentalancia <address@hidden>.

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

Summary of changes:
 THANKS          |    1 +
 doc/libidn.texi |    8 ++++++++
 2 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/THANKS b/THANKS
index 10e2dc0..4128fad 100644
--- a/THANKS
+++ b/THANKS
@@ -94,6 +94,7 @@ Stepan Golosunov <address@hidden>
 "Andrew O. Shadoura" <address@hidden>
 Roman Mamedov <address@hidden>
 Waqas Hussain <address@hidden>
+Guido Trentalancia <address@hidden>
 
 ----------------------------------------------------------------------
 Copying and distribution of this file, with or without modification,
diff --git a/doc/libidn.texi b/doc/libidn.texi
index c915ffe..044b726 100644
--- a/doc/libidn.texi
+++ b/doc/libidn.texi
@@ -501,6 +501,14 @@ more information.  Here, @code{IMPL} is @code{pnet} or 
@code{mono},
 indicating whether the PNET @command{cscc} compiler or the Mono
 @command{mcs} compiler should be used, respectively.
 
address@hidden --disable-valgrind-tests
+Disable running the self-checks under Valgrind
+(@url{http://valgrind.org/}).  Normally Valgrind does not cause
+problems and can detect some severe memory errors.  If you are getting
+errors from Valgrind that are caused by the compiler or libc (possibly
+as a result of special optimization flags), you may use this option to
+disable the use of Valgrind.
+
 @end table
 
 For the complete list, refer to the output from @code{configure


hooks/post-receive
-- 
GNU libidn