grep - News: grep-2.7 released [stable]

grep-2.7 released [stable]

Item posted by Jim Meyering <meyering> on Mon 20 Sep 2010 04:29:23 PM UTC.

This is to announce grep-2.7.

grep is a tool to search for strings inside a file.

This release fixes a few bug fixes and includes two features.
See the NEWS below, or for a more complete summary of changes and
contributors, see:
  http://git.sv.gnu.org/gitweb/?p=grep.git;a=shortlog;h=v2.7
or run this command from a git-cloned grep directory:
  git shortlog v2.6.3..v2.7

Here are the compressed sources:
  http://ftp.gnu.org/gnu/grep/grep-2.7.tar.gz   (1.5MB)
  http://ftp.gnu.org/gnu/grep/grep-2.7.tar.xz   (904KB)

Here are the GPG detached signatures[*]:
  http://ftp.gnu.org/gnu/grep/grep-2.7.tar.gz.sig
  http://ftp.gnu.org/gnu/grep/grep-2.7.tar.xz.sig

To reduce load on the main server, use a mirror listed at:
  http://www.gnu.org/order/ftp.html

[*] You can use either of the above signature files 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.7.tar.gz.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 B9AB9A16

and rerun the `gpg --verify' command.

This release was bootstrapped with the following tools:
  Autoconf 2.67.65-9144
  Automake 1.11a
  Gnulib v0.0-4248-ge2b0e1a

NEWS

* Noteworthy changes in release 2.7 (2010-09-16) [stable]

** Bug fixes

  grep --include=FILE works once again, rather than working like --exclude=FILE
  [bug introduced in grep-2.6]

  Searching with grep -Fw for an empty string would not match an
  empty line. [bug present since "the beginning"]

  X{0,0} is implemented correctly.  It used to be a synonym of X{0,1}.
  [bug present since "the beginning"]

  In multibyte locales, regular expressions including backreferences
  no longer exhibit quadratic complexity (i.e., they are orders
  of magnitude faster). [bug present since multi-byte character set
  support was introduced in 2.5.2]

  In UTF-8 locales, regular expressions including "." can be orders
  of magnitude faster.  For example, "grep ." is now twice as fast
  as "grep -v ^$", instead of being immensely slower.  It remains
  slow in other multibyte locales. [bug present since multi-byte
  character set support was introduced in 2.5.2]

  --mmap was meant to be ignored in 2.6.x, but it was instead
  removed by mistake.  [bug introduced in 2.6]

** New features

  grep now diagnoses (and fails with exit status 2) commonly mistyped
  regular expression like [:space:], [:digit:], etc.  Before, those were
  silently interpreted as [ac:eps] and [dgit:] respectively.  Virtually
  all who make that class of mistake should have used [[:space:]] or
  [[:digit:]].  This new behavior is disabled when the POSIXLY_CORRECT
  environment variable is set.

  On systems using glibc, grep can support equivalence classes.  However,
  whether they actually work depends on glibc's locale definitions.