From: Florian Krohm <florian@eich-krohm.de>
Date: Thu, 24 Jul 2014 19:26:32 +0000 (+0000)
Subject: Update a comment so it won't need updating in the future.
X-Git-Tag: svn/VALGRIND_3_10_0~251
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=7a00b0cb5b200c44e45db067bb2c71ed51db5db4;p=thirdparty%2Fvalgrind.git

Update a comment so it won't need updating in the future.
No functional change.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14187
---

diff --git a/coregrind/m_demangle/demangle.c b/coregrind/m_demangle/demangle.c
index 72832a464b..6220dddaf8 100644
--- a/coregrind/m_demangle/demangle.c
+++ b/coregrind/m_demangle/demangle.c
@@ -74,15 +74,12 @@
    completely unmodified.  We use vg_libciface.h as a way to
    impedance-match the libiberty code into our own framework.
 
-   The current code is from libiberty in the gcc tree, gcc svn
-   r181975, dated 12 Dec 2011 (when the gcc trunk was in Stage 3
-   leading up to a gcc-4.7 release).  As of r141363, libiberty is LGPL
-   2.1, which AFAICT is compatible with "GPL 2 or later" and so is OK
-   for inclusion in Valgrind.
-
-   To update to a newer libiberty, it might be simplest to svn diff
-   the gcc tree libibery against r181975 and then apply those diffs
-   here. */
+   The libiberty code included here was taken from the GCC repository
+   and is released under the LGPL 2.1 license, which AFAICT is compatible
+   with "GPL 2 or later" and so is OK for inclusion in Valgrind.
+
+   To update to a newer libiberty, use the "update-demangler" script
+   which is included in the valgrind repository. */
 
 /* This is the main, standard demangler entry point. */