This is to announce grep-2.14, a stable release. It is unusual to make a new release after so few changes, but it is even more unusual to discover that a command like grep -i '^$' can malfunction. It could report a match even though there was none.
There have been 17 commits by 2 people in the 7 weeks since 2.13. See the NEWS below for a brief summary. Thanks to everyone who has contributed! The following people contributed changes to this release: Jim Meyering (12) Paul Eggert (5) 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.14 or run this command from a git-cloned grep directory: git shortlog v2.13..v2.14 To summarize the 72 gnulib-related changes, run these commands From a git-cloned grep directory: git checkout v2.14 git submodule summary v2.13 Here are the compressed sources and a GPG detached signature[*]: http://ftp.gnu.org/gnu/grep/grep-2.14.tar.xz http://ftp.gnu.org/gnu/grep/grep-2.14.tar.xz.sig Use a mirror for higher download bandwidth: http://ftpmirror.gnu.org/grep/grep-2.14.tar.xz http://ftpmirror.gnu.org/grep/grep-2.14.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.14.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.19-1bb10 Automake 1.12a Gnulib v0.0-7573-ga451aa0 ================================================================== NEWS * Noteworthy changes in release 2.14 (2012-08-20) [stable] ** Bug fixes grep -i '^$' could exit 0 (i.e., report a match) in a multi-byte locale, even though there was no match, and the command generated no output. E.g., seq 2 | LC_ALL=en_US.utf8 grep -il '^$' would mistakenly print "(standard input)". Related, seq 9 | LC_ALL=en_US.utf8 grep -in '^$' would print "2:4:6:8:10:12:14:16" and exit 0. Now it prints nothing and exits with status of 1. [bug introduced in grep-2.6] 'grep' no longer falsely reports text files as being binary on file systems that compress contents or that store tiny contents in metadata. ----- also posted as: https://savannah.gnu.org/forum/forum.php?forum_id=7338
pgpnETQqglCxr.pgp
Description: PGP signature
_______________________________________________ GNU Announcement mailing list <info-gnu@gnu.org> https://lists.gnu.org/mailman/listinfo/info-gnu