]> git.wh0rd.org Git - nano.git/commitdiff
mention the removal of the workaround for glibc 2.2.3's broken regexec()
authorDavid Lawrence Ramsey <pooka109@gmail.com>
Mon, 5 Jun 2006 15:44:55 +0000 (15:44 +0000)
committerDavid Lawrence Ramsey <pooka109@gmail.com>
Mon, 5 Jun 2006 15:44:55 +0000 (15:44 +0000)
in UPGRADE too

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@3625 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

ChangeLog
UPGRADE

index 148c58848e9b569deb43edd6c196b244e599162d..1ddf4fc0e8a003ad97ccb9830569b561b4270f3c 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -142,7 +142,7 @@ CVS code -
          replace it with a FAQ entry explaining the problem, since it
          could break anything using extended regular expressions, and
          glibc 2.2.3 is old.  Changes to configure.ac, faq.html,
-         nano.h, and proto.h; removal of safe_regexec(). (DLR)
+         nano.h, proto.h, and UPGRADE; removal of safe_regexec(). (DLR)
 - browser.c:
   do_browser()
        - Reference NANO_GOTODIR_(ALT|F)?KEY instead of
diff --git a/UPGRADE b/UPGRADE
index 24f7cff4bb277bfedc17e670b47a9450db31912d..030711cde831deaa421b8e4f225a61c6971c4eb7 100644 (file)
--- a/UPGRADE
+++ b/UPGRADE
@@ -48,6 +48,10 @@ Visible changes since 1.2
   - Many more functions available at the statusbar prompt: moving to the
     next or previous word, searching for matching brackets, "Verbatim
     Input" mode, etc.
+  - The glibc 2.2.3 crashes involving extended regular expressions are
+    no longer worked around, as they can break anything using extended
+    regular expressions, and glibc 2.2.3 is old.  You should upgrade to
+    at least glibc 2.2.4.
 
 * File Handling
   - Automatic adding of newlines to the ends of files without them can