-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 This is to announce grep-2.15, a stable, bug-fix release.
There have been 57 commits by 9 people in the 62 weeks since 2.14. See the NEWS below for a brief summary. Thanks to everyone who has contributed! The following people contributed changes to this release: Corinna Vinschen (1) Eric Blake (2) Jaroslav Škarvada (1) Jim Meyering (31) Mike Haertel (1) Paolo Bonzini (3) Paul Eggert (15) Petr Pisar (1) Stefano Lattarini (2) Jim [on behalf of the grep maintainers] ================================================================== Here is the GNU grep home page: http://gnu.org/s/grep/ For a summary of changes and contributors, see: http://git.sv.gnu.org/gitweb/?p=grep.git;a=shortlog;h=v2.15 or run this command from a git-cloned grep directory: git shortlog v2.14..v2.15 To summarize the 486 gnulib-related changes, run these commands from a git-cloned grep directory: git checkout v2.15 git submodule summary v2.14 Here are the compressed sources and a GPG detached signature[*]: http://ftp.gnu.org/gnu/grep/grep-2.15.tar.xz http://ftp.gnu.org/gnu/grep/grep-2.15.tar.xz.sig Use a mirror for higher download bandwidth: http://ftpmirror.gnu.org/grep/grep-2.15.tar.xz http://ftpmirror.gnu.org/grep/grep-2.15.tar.xz.sig [*] Use a .sig file to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this: gpg --verify grep-2.15.tar.xz.sig If that command fails because you don't have the required public key, then run this command to import it: gpg --keyserver keys.gnupg.net --recv-keys 7FD9FCCB000BEEEE and rerun the 'gpg --verify' command. This release was bootstrapped with the following tools: Autoconf 2.69.112-f181 Automake 1.99a Gnulib v0.0-8059-g974b76b NEWS * Noteworthy changes in release 2.15 (2013-10-26) [stable] ** Bug fixes grep's \s and \S failed to work with multi-byte white space characters. For example, \s would fail to match a non-breaking space, and this would print nothing: printf '\xc2\xa0' | LC_ALL=en_US.UTF-8 grep '\s' A related bug is that \S would mistakenly match an invalid multibyte character. For example, the following would match: printf '\x82\n' | LC_ALL=en_US.UTF-8 grep '^\S$' [bug present since grep-2.6] grep -i would segfault on systems using UTF-16-based wchar_t (Cygwin) when converting an input string containing certain 4-byte UTF-8 sequences to lower case. The conversions to wchar_t and back to a UTF-8 multibyte string did not take surrogate pairs into account. [bug present since at least grep-2.6, though the segfault is new with 2.13] grep -E would segfault when given a regexp like '([^.]*[M]){1,2}' for any multibyte character M. [bug introduced in grep-2.6, which would segfault, but 2.7 and 2.8 had no problem, and 2.9 through 2.14 would hit a failed assertion. ] grep -F would get stuck in an infinite loop when given a search string that is an invalid byte sequence in the current locale and that matches the bytes of the input twice on a line. Now grep fails with exit status 1. grep -P could misbehave. While multi-byte mode is only supported by PCRE with UTF-8 locales, grep did not activate it. This would cause failures to match multibyte characters against some regular expressions, especially those including the '.' or '\p' metacharacters. ** New features grep -P can now use a just-in-time compiler to greatly speed up matches, This feature is transparent to the user; no flag is required to enable it. It is only available if the corresponding support in the PCRE library is detected when grep is compiled. - ----- also posted as: https://savannah.gnu.org/forum/forum.php?forum_id=7763 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (Darwin) iQJ8BAEBCgBmBQJSa/6DXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxNTVEM0ZDNTAwQzgzNDQ4NkQxRUVBNjc3 RkQ5RkNDQjAwMEJFRUVFAAoJEH/Z/MsAC+7uXNwQAIqjvk3OBAOOV4RShDdhH9dl e+fTaw35dNGGsyUzSIKFh0rndSvAKSEADZvkvtPEaqw6tXpAOLtHhhydZWw+QV8B Ph5oE1Ls5IQJaJHM5X7wFMP3t74Lx41BW7ZxIv51JpneG9dVGHo3LnI73aRlgBRc nOkbW4ZNAplSGQPAl8elQkg/4lHYCFn4cnSjca5AZg/B1dA3RmB9247PcB+TFeC3 yMY44uoG2EFN4I36NiRd1pvOfc7DwAs77UUab0d7JuMaxIZ7u7PFqKPDMwm9PqNV mY7Izevqco0XFNdPSp3VtoYv7dbwl+mbQvOLYvJjO3SVBjpERmXqqKns1bIWgRDv fbfaJAiX46bSXPesI/UcPZW+REd8y9hTO2Yp2bJgnPOotKSt2dNS5VqGVRjyE/3P K87c5vm9rzQgc2aTIY54U8zcPeYsArlFCCe1pKlHdcJ2zZNak6ayfSV2ag9O1WUs SIMlwf7IK72NbLRMH0ysPfFN8oCFX2mO60L22VSKKJIFs4JozEM95KSgj7iXVDsU 06m1+mO1tB/C31sW+Tu9TNBMGXNtxkRrhxvh16RafZWYMnErzxxvaZZrKRESn2sq mCuwDWykXBDcF4PjIQ2NmBrzm1VcLcYmwhwLuJs3RAMY9/0kJn+gJJZiRjbRjTR3 09pXU8OJL1jbsBcHC4YC =UolA -----END PGP SIGNATURE----- _______________________________________________ GNU Announcement mailing list <info-gnu@gnu.org> https://lists.gnu.org/mailman/listinfo/info-gnu