This is to announce grep-3.11, a stable release.
This release makes PCRE patterns like [\d] work again, at the expense of
reverting to the behavior of grep 3.8, in that patterns like \w and \b go
back to using ASCII rather than Unicode interpretations. However, if you
build grep using pcre2 newer than 10.42, then \w and \b do work properly.
Special thanks to Bruno Haible for all his fine work improving gnulib
and helping to test tools like grep that use it.
I bootstrapped this release with very recent gnulib, autoconf and
automake, hoping to flush out any bugs before releases of the latter two.
There have been 22 commits by 4 people in the 7 weeks since 3.10.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Carlo Marcelo Arenas Belón (2)
Jim Meyering (13)
Josh Soref (1)
Paul Eggert (6)
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=v3.11
or run this command from a git-cloned grep directory:
git shortlog v3.10..v3.11
Here are the compressed sources:
https://ftp.gnu.org/gnu/grep/grep-3.11.tar.gz (2.7MB)
https://ftp.gnu.org/gnu/grep/grep-3.11.tar.xz (1.7MB)
Here are the GPG detached signatures:
https://ftp.gnu.org/gnu/grep/grep-3.11.tar.gz.sig
https://ftp.gnu.org/gnu/grep/grep-3.11.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA1 and SHA256 checksums:
73ef2b57c32a81b5671a853dd33efc58ab6c23f7 grep-3.11.tar.gz
HzEBSVPnHDzdztuXaSrXYgy51tBPvcGeDY3YNvh2Irs= grep-3.11.tar.gz
955146a0a4887eca33606e391481bbef37055b86 grep-3.11.tar.xz
HbKu3eidDepCsW2VKPiUyNFdrk4ZC1muzHj1qVEnbqs= grep-3.11.tar.xz
Verify the base64 SHA256 checksum with cksum -a sha256 --check
from coreutils-9.2 or OpenBSD's cksum since 2007.
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-3.11.tar.gz.sig
The signature should match the fingerprint of the following key:
pub rsa4096/0x7FD9FCCB000BEEEE 2010-06-14 [SCEA]
Key fingerprint = 155D 3FC5 00C8 3448 6D1E EA67 7FD9 FCCB 000B EEEE
uid [ unknown] Jim Meyering <jim@meyering.net>
uid [ unknown] Jim Meyering <meyering@fb.com>
uid [ unknown] Jim Meyering <meyering@gnu.org>
If that command fails because you don't have the required public key,
or that public key has expired, try the following commands to retrieve
or refresh it, and then rerun the 'gpg --verify' command.
gpg --locate-external-key jim@meyering.net
gpg --recv-keys 7FD9FCCB000BEEEE
wget -q -O- 'https://savannah.gnu.org/project/release-gpgkeys.php?group=grep&download=1' | gpg --import -
As a last resort to find the key, you can try the official GNU
keyring:
wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg
gpg --keyring gnu-keyring.gpg --verify grep-3.11.tar.gz.sig
This release was bootstrapped with the following tools:
Autoconf 2.72c.20-9c018
Automake 1.16i
Gnulib v0.1-6153-gc2a5953f17
NEWS
* Noteworthy changes in release 3.11 (2023-05-13) [stable]
** Bug fixes
With -P, patterns like [\d] now work again. Fixing this has caused
grep to revert to the behavior of grep 3.8, in that patterns like \w
and \b go back to using ASCII rather than Unicode interpretations.
However, future versions of GNU grep and/or PCRE2 are likely to fix
this and change the behavior of \w and \b back to Unicode again,
without breaking [\d] as 3.10 did.
[bug introduced in grep 3.10]
grep no longer fails on files dated after the year 2038,
when running on 32-bit x86 and ARM hosts using glibc 2.34+.
[bug introduced in grep 3.9]
grep -P no longer fails to match patterns using negated classes
like \D or \W when linked with PCRE2 10.34 or newer.
[bug introduced in grep 3.8]
** Changes in behavior
grep --version now prints a line describing the version of PCRE2 it uses.
For example, it prints this when built with the very latest from git:
grep -P uses PCRE2 10.43-DEV 2023-04-14
or this with what's currently available in Fedora 37:
grep -P uses PCRE2 10.40 2022-04-14
previous versions of grep wouldn't respect the user provided settings for
PCRE_CFLAGS and PCRE_LIBS when building if a libpcre2-8 pkg-config module
was found.
This is to announce grep-3.10, a stable release,
fixing a bug with -P and \d. TL;DR, grep-3.9 would do this:
$ LC_ALL=en_US.UTF-8 grep -P '\d' <<< ٠١٢٣٤٥٦٧٨٩
٠١٢٣٤٥٦٧٨٩
It should print nothing, like it has always done.
For more detail, see https://lists.gnu.org/r/bug-grep/2023-03/msg00005.html
Thanks to Paul Eggert for catching the \D variant and to Bruno Haible
for assiduously tending gnulib and for testing grep on so many
different systems.
There have been 12 commits by 2 people in the 17 days since 3.9.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (8)
Paul Eggert (4)
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=v3.10
or run this command from a git-cloned grep directory:
git shortlog v3.9..v3.10
Here are the compressed sources:
https://ftp.gnu.org/gnu/grep/grep-3.10.tar.gz (2.7MB)
https://ftp.gnu.org/gnu/grep/grep-3.10.tar.xz (1.7MB)
Here are the GPG detached signatures:
https://ftp.gnu.org/gnu/grep/grep-3.10.tar.gz.sig
https://ftp.gnu.org/gnu/grep/grep-3.10.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA1 and SHA256 checksums:
7d3d830703183532f0b66619f0b148827e86eda7 grep-3.10.tar.gz
3nsh2OM0jqZWnG/Vc06QoxFp72JCnqPc5Ipvwd2F0mA= grep-3.10.tar.gz
b8413017681fcd6249e0d0fb9c78225944074f23 grep-3.10.tar.xz
JO+ltZX7WnEAh5tRuIaKC7h6ccGD0CxMYCYzuIr2hVs= grep-3.10.tar.xz
Verify the base64 SHA256 checksum with cksum -a sha256 --check
from coreutils-9.2 or OpenBSD's cksum since 2007.
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-3.10.tar.gz.sig
The signature should match the fingerprint of the following key:
pub rsa4096/0x7FD9FCCB000BEEEE 2010-06-14 [SCEA]
Key fingerprint = 155D 3FC5 00C8 3448 6D1E EA67 7FD9 FCCB 000B EEEE
uid [ unknown] Jim Meyering <jim@meyering.net>
uid [ unknown] Jim Meyering <meyering@fb.com>
uid [ unknown] Jim Meyering <meyering@gnu.org>
If that command fails because you don't have the required public key,
or that public key has expired, try the following commands to retrieve
or refresh it, and then rerun the 'gpg --verify' command.
gpg --locate-external-key jim@meyering.net
gpg --recv-keys 7FD9FCCB000BEEEE
wget -q -O- 'https://savannah.gnu.org/project/release-gpgkeys.php?group=grep&download=1' | gpg --import -
As a last resort to find the key, you can try the official GNU
keyring:
wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg
gpg --keyring gnu-keyring.gpg --verify grep-3.10.tar.gz.sig
This release was bootstrapped with the following tools:
Autoconf 2.72a.92-8db0
Automake 1.16i
Gnulib v0.1-5916-gf61570c0ef
NEWS
* Noteworthy changes in release 3.10 (2023-03-22) [stable]
** Bug fixes
With -P, \d now matches only ASCII digits, regardless of PCRE
options/modes. The changes in grep-3.9 to make \b and \w work
properly had the undesirable side effect of making \d also match
e.g., the Arabic digits: ٠١٢٣٤٥٦٧٨٩. With grep-3.9, -P '\d+'
would match that ten-digit (20-byte) string. Now, to match such
a digit, you would use \p{Nd}. Similarly, \D is now mapped to [^0-9].
[bug introduced in grep 3.9]
This is to announce grep-3.9, a stable release.
The NEWS below describes the two main bug fixes since 3.8.
There have been 38 commits by 4 people in the 26 weeks since 3.8.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Bruno Haible (2)
Carlo Marcelo Arenas Belón (2)
Jim Meyering (11)
Paul Eggert (23)
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=v3.9
or run this command from a git-cloned grep directory:
git shortlog v3.8..v3.9
Here are the compressed sources:
https://ftp.gnu.org/gnu/grep/grep-3.9.tar.gz (2.7MB)
https://ftp.gnu.org/gnu/grep/grep-3.9.tar.xz (1.7MB)
Here are the GPG detached signatures:
https://ftp.gnu.org/gnu/grep/grep-3.9.tar.gz.sig
https://ftp.gnu.org/gnu/grep/grep-3.9.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA1 and SHA256 checksums:
f84afbfc8d6e38e422f1f2fc458b0ccdbfaeb392 grep-3.9.tar.gz
7ZF6C+5DtxJS9cpR1IwLjQ7/kAfSpJCCbEJb9wmfWT8= grep-3.9.tar.gz
bcaa3f0c4b81ae4192c8d0a2be3571a14ea27383 grep-3.9.tar.xz
q80RQJ7iPUyvNf60IuU7ushnAUz+7TE7tfSIrKFwtZk= grep-3.9.tar.xz
Verify the base64 SHA256 checksum with cksum -a sha256 --check
from coreutils-9.2 or OpenBSD's cksum since 2007.
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-3.9.tar.gz.sig
The signature should match the fingerprint of the following key:
pub rsa4096/0x7FD9FCCB000BEEEE 2010-06-14 [SCEA]
Key fingerprint = 155D 3FC5 00C8 3448 6D1E EA67 7FD9 FCCB 000B EEEE
uid [ unknown] Jim Meyering <jim@meyering.net>
uid [ unknown] Jim Meyering <meyering@fb.com>
uid [ unknown] Jim Meyering <meyering@gnu.org>
If that command fails because you don't have the required public key,
or that public key has expired, try the following commands to retrieve
or refresh it, and then rerun the 'gpg --verify' command.
gpg --locate-external-key jim@meyering.net
gpg --recv-keys 7FD9FCCB000BEEEE
wget -q -O- 'https://savannah.gnu.org/project/release-gpgkeys.php?group=grep&download=1' | gpg --import -
As a last resort to find the key, you can try the official GNU
keyring:
wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg
gpg --keyring gnu-keyring.gpg --verify grep-3.9.tar.gz.sig
This release was bootstrapped with the following tools:
Autoconf 2.72a.65-d081
Automake 1.16i
Gnulib v0.1-5861-g2ba7c75ed1
NEWS
* Noteworthy changes in release 3.9 (2023-03-05) [stable]
** Bug fixes
With -P, some non-ASCII UTF8 characters were not recognized as
word-constituent due to our omission of the PCRE2_UCP flag. E.g.,
given f(){ echo Perú|LC_ALL=en_US.UTF-8 grep -Po "$1"; } and
this command, echo $(f 'r\w'):$(f '.\b'), before it would print ":r".
After the fix, it prints the correct results: "rú:ú".
When given multiple patterns the last of which has a back-reference,
grep no longer sometimes mistakenly matches lines in some cases.
[Bug#36148#13 introduced in grep 3.4]
This is to announce grep-3.8, a stable release.
Special thanks to Carlo Arenas for adding PCRE2 support
and to Paul Eggert for his many fine changes.
There have been 104 commits by 6 people in the 55 weeks since 3.7.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Carlo Marcelo Arenas Belón (2)
Helge Kreutzmann (1)
Jim Meyering (27)
Ondřej Fiala (1)
Paul Eggert (71)
Ulrich Eckhardt (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=v3.8
or run this command from a git-cloned grep directory:
git shortlog v3.7..v3.8
To summarize the 432 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v3.8
git submodule summary v3.7
==================================================================
Here are the compressed sources:
https://ftp.gnu.org/gnu/grep/grep-3.8.tar.gz (2.8MB)
https://ftp.gnu.org/gnu/grep/grep-3.8.tar.xz (1.7MB)
Here are the GPG detached signatures:
https://ftp.gnu.org/gnu/grep/grep-3.8.tar.gz.sig
https://ftp.gnu.org/gnu/grep/grep-3.8.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA1 and SHA256 checksums:
eb3bf741fefb2d64e67d9ea6d74c723ea0efddb6 grep-3.8.tar.gz
jeYKUWnAwf3YFwvZO72ldbh7/Pp95jGbi9YNwgvi+5c grep-3.8.tar.gz
6d0d32cabaf44efac9e1d2c449eb041525c54b2e grep-3.8.tar.xz
SY18wbT7CBkE2HND/rtzR1z3ceQk+35hQa/2YBOrw4I grep-3.8.tar.xz
Each SHA256 checksum is base64 encoded, preferred over the much
longer hexadecimal encoding that most checksum tools default to.
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-3.8.tar.gz.sig
The signature should match the fingerprint of the following key:
pub rsa4096/0x7FD9FCCB000BEEEE 2010-06-14 [SCEA]
Key fingerprint = 155D 3FC5 00C8 3448 6D1E EA67 7FD9 FCCB 000B EEEE
uid Jim Meyering <jim@meyering.net>
If that command fails because you don't have the required public key,
or that public key has expired, try the following commands to retrieve
or refresh it, and then rerun the 'gpg --verify' command.
gpg --locate-external-key jim@meyering.net
gpg --recv-keys 7FD9FCCB000BEEEE
wget -q -O- 'https://savannah.gnu.org/project/release-gpgkeys.php?group=grep&download=1' | gpg --import -
As a last resort to find the key, you can try the official GNU
keyring:
wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg
gpg --keyring gnu-keyring.gpg --verify grep-3.8.tar.gz.sig
This release was bootstrapped with the following tools:
Autoconf 2.72a.55-bc66c
Automake 1.16i
Gnulib v0.1-5279-g19435dc207
==================================================================
NEWS
* Noteworthy changes in release 3.8 (2022-09-02) [stable]
** Changes in behavior
The -P option is now based on PCRE2 instead of the older PCRE,
thanks to code contributed by Carlo Arenas.
The egrep and fgrep commands, which have been deprecated since
release 2.5.3 (2007), now warn that they are obsolescent and should
be replaced by grep -E and grep -F.
The confusing GREP_COLOR environment variable is now obsolescent.
Instead of GREP_COLOR='xxx', use GREP_COLORS='mt=xxx'. grep now
warns if GREP_COLOR is used and is not overridden by GREP_COLORS.
Also, grep now treats GREP_COLOR like GREP_COLORS by silently
ignoring it if it attempts to inject ANSI terminal escapes.
Regular expressions with stray backslashes now cause warnings, as
their unspecified behavior can lead to unexpected results.
For example, '\a' and 'a' are not always equivalent
<https://bugs.gnu.org/39678>. Similarly, regular expressions or
subexpressions that start with a repetition operator now also cause
warnings due to their unspecified behavior; for example, *a(+b|{1}c)
now has three reasons to warn. The warnings are intended as a
transition aid; they are likely to be errors in future releases.
Regular expressions like [:space:] are now errors even if
POSIXLY_CORRECT is set, since POSIX now allows the GNU behavior.
** Bug fixes
In locales using UTF-8 encoding, the regular expression '.' no
longer sometimes fails to match Unicode characters U+D400 through
U+D7FF (some Hangul Syllables, and Hangul Jamo Extended-B) and
Unicode characters U+108000 through U+10FFFF (half of Supplemental
Private Use Area plane B).
[bug introduced in grep 3.4]
The -s option no longer suppresses "binary file matches" messages.
[Bug#51860 introduced in grep 3.5]
** Documentation improvements
The manual now covers unspecified behavior in patterns like \x, (+),
and range expressions outside the POSIX locale.
This is to announce grep-3.7, a stable release.
There have been 33 commits by 6 people in the 40 weeks since 3.6.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Helge Kreutzmann (1)
Jim Meyering (15)
Kevin Locke (2)
Marek Suppa (1)
Mateusz Okulus (1)
Paul Eggert (13)
There were also 855 changes via the gnulib submodule.
==================================================================
Here is the GNU grep home page:
http://gnu.org/s/grep/
Here are the compressed sources:
https://ftp.gnu.org/gnu/grep/grep-3.7.tar.gz (2.6MB)
https://ftp.gnu.org/gnu/grep/grep-3.7.tar.xz (1.6MB)
Here are the GPG detached signatures[*]:
https://ftp.gnu.org/gnu/grep/grep-3.7.tar.gz.sig
https://ftp.gnu.org/gnu/grep/grep-3.7.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
Here are the SHA1 and SHA256 checksums:
5359ea0105cedfa21a63c89b22e0d7b41b016a40 grep-3.7.tar.gz
wisM8tT2u+WZyQI4foBYmQ4e7pmu8zOiA4KeX9Pbs0I grep-3.7.tar.gz
4d56da85e468e4012c81533a22052014a4c98b17 grep-3.7.tar.xz
XBDaMSRgrschmE1dgyRtJFIOxDjdSNerWgXbwNbWgjw grep-3.7.tar.xz
The SHA256 checksum is base64 encoded, instead of the
hexadecimal encoding that most checksum tools default to.
[*] 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-3.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 7FD9FCCB000BEEEE
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.71
Automake 1.16d
Gnulib v0.1-4847-g1cb09be022
===============================
NEWS
* Noteworthy changes in release 3.7 (2021-08-14) [stable]
** Changes in behavior
Use of the --unix-byte-offsets (-u) option now evokes a warning.
Since 3.1, this Windows-only option has had no effect.
** Bug fixes
Preprocessing N patterns would take at least O(N^2) time when too many
patterns hashed to too few buckets. This now takes seconds, not days:
: | grep -Ff <(seq 6400000 | tr 0-9 A-J)
[Bug#44754 introduced in grep 3.5]
This is to announce grep-3.6, a stable release.
There have been 18 commits by 3 people in the 6 weeks since 3.5.
This release has two important changes, a fix for a bug introduced in
grep-3.2 (from late 2018) and the removal of support for the long-deprecated
GREP_OPTIONS envvar. See the NEWS below for more detail.
Thanks again to Norihiro Tanaka and Paul Eggert,
and to everyone else who has contributed.
The following people contributed changes to this release:
Jim Meyering (9)
Norihiro Tanaka (3)
Paul Eggert (6)
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=v3.6
or run this command from a git-cloned grep directory:
git shortlog v3.5..v3.6
To summarize the 65 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v3.6
git submodule summary v3.5
==================================================================
Here are the compressed sources:
https://ftp.gnu.org/gnu/grep/grep-3.6.tar.gz (2.6MB)
https://ftp.gnu.org/gnu/grep/grep-3.6.tar.xz (1.6MB)
Here are the GPG detached signatures[*]:
https://ftp.gnu.org/gnu/grep/grep-3.6.tar.gz.sig
https://ftp.gnu.org/gnu/grep/grep-3.6.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
[*] 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-3.6.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 7FD9FCCB000BEEEE
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.69c
Automake 1.16b
Gnulib v0.1-3992-gbd90572c0
==================================================================
NEWS
* Noteworthy changes in release 3.6 (2020-11-08) [stable]
** Changes in behavior
The GREP_OPTIONS environment variable no longer affects grep's behavior.
The variable was declared obsolescent in grep 2.21 (2014), and since
then any use had caused grep to issue a diagnostic.
** Bug fixes
grep's DFA matcher performed an invalid regex transformation
that would convert an ERE like a+a+a+ to a+a+, which would make
grep a+a+a+ mistakenly match "aa".
[Bug#44351 introduced in grep 3.2]
grep -P now reports the troublesome input filename upon PCRE execution
failure. Before, searching many files for something rare might fail with
just "exceeded PCRE's backtracking limit". Now, it also reports which file
triggered the failure.
This is to announce grep-3.5, a stable release.
Thanks especially to Paul Eggert, Norihiro Tanaka and Bruno Haible
for changes both in grep proper and in gnulib.
There have been 56 commits by 3 people in the 38 weeks since 3.4.
See the NEWS below for a summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (22)
Norihiro Tanaka (1)
Paul Eggert (33)
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=v3.5
or run this command from a git-cloned grep directory:
git shortlog v3.4-almost..v3.5
To summarize the 806 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v3.5
git submodule summary v3.4-almost
==================================================================
Here are the compressed sources:
https://ftp.gnu.org/gnu/grep/grep-3.5.tar.gz (2.6MB)
https://ftp.gnu.org/gnu/grep/grep-3.5.tar.xz (1.6MB)
Here are the GPG detached signatures[*]:
https://ftp.gnu.org/gnu/grep/grep-3.5.tar.gz.sig
https://ftp.gnu.org/gnu/grep/grep-3.5.tar.xz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
[*] 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-3.5.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 7FD9FCCB000BEEEE
and rerun the 'gpg --verify' command.
This release was bootstrapped with the following tools:
Autoconf 2.69c
Automake 1.16b
Gnulib v0.1-3927-g02b29b878
==================================================================
NEWS
* Noteworthy changes in release 3.5 (2020-09-27) [stable]
** Changes in behavior
The message that a binary file matches is now sent to standard error
and the message has been reworded from "Binary file FOO matches" to
"grep: FOO: binary file matches", to avoid confusion with ordinary
output or when file names contain spaces and the like, and to be
more consistent with other diagnostics. For example, commands
like 'grep PATTERN FILE | wc' no longer add 1 to the count of
matching text lines due to the presence of the message. Like other
stderr messages, the message is now omitted if the --no-messages
(-s) option is given.
Two other stderr messages now use the typical form too. They are
now "grep: FOO: warning: recursive directory loop" and "grep: FOO:
input file is also the output".
The --files-without-match (-L) option has reverted to its behavior
in grep 3.1 and earlier. That is, grep -L again succeeds when a
line is selected, not when a file is listed. The behavior in grep
3.2 through 3.4 was causing compatibility problems.
** Bug fixes
grep -I no longer issues a spurious "Binary file FOO matches" line.
[Bug#33552 introduced in grep 2.23]
In UTF-8 locales, grep -w no longer ignores a multibyte word
constituent just before what would otherwise be a word match.
[Bug#43225 introduced in grep 2.28]
grep -i no longer mishandles ASCII characters that match multibyte
characters. For example, 'LC_ALL=tr_TR.utf8 grep -i i' no longer
dumps core merely because 'i' matches 'İ' (U+0130 LATIN CAPITAL
LETTER I WITH DOT ABOVE) in Turkish when ignoring case.
[Bug#43577 introduced partly in grep 2.28 and partly in grep 3.4]
A performance regression with -E and many patterns has been mostly fixed.
"Mostly" as there is a performance tradeoff between Bug#22357 and Bug#40634.
[Bug#40634 introduced in grep 2.28]
A performance regression with many duplicate patterns has been fixed.
[Bug#43040 introduced in grep 3.4]
An N^2 RSS performance regression with many patterns has been fixed
in common cases (no backref, and no use of -o or --color).
With only 80,000 lines of /usr/share/dict/linux.words, the following
would use 100GB of RSS and take 3 minutes. With the fix, it used less
than 400MB and took less than one second:
head -80000 /usr/share/dict/linux.words > w; grep -vf w w
[Bug#43527 introduced in grep 3.4]
** Build-related
"make dist" builds .tar.gz files again, as they are still used in
some barebones builds.
This is to announce grep-3.4, a stable release.
Special thanks to Paul Eggert and Norihiro Tanaka for their many fine contributions.
There have been 71 commits by 4 people in the 54 weeks since 3.3.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (31)
Norihiro Tanaka (5)
Paul Eggert (34)
Zev Weiss (1)
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=v3.4
or run this command from a git-cloned grep directory:
git shortlog v3.3..v3.4
To summarize the 819 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v3.4
git submodule summary v3.3
==================================================================
Here are the compressed sources and a GPG detached signature[*]:
https://ftp.gnu.org/gnu/grep/grep-3.4.tar.xz
https://ftp.gnu.org/gnu/grep/grep-3.4.tar.xz.sig
Use a mirror for higher download bandwidth:
https://ftpmirror.gnu.org/grep/grep-3.4.tar.xz
https://ftpmirror.gnu.org/grep/grep-3.4.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-3.4.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.197-b8fd7-dirty
Automake 1.16a
Gnulib v0.1-3121-gc3c36de58
==================================================================
NEWS
* Noteworthy changes in release 3.4 (2020-01-02) [stable]
** New features
The new --no-ignore-case option causes grep to observe case
distinctions, overriding any previous -i (--ignore-case) option.
** Bug fixes
'.' no longer matches some invalid byte sequences in UTF-8 locales.
[bug introduced in grep 2.7]
grep -Fw can no longer false match in non-UTF-8 multibyte locales
For example, this command would erroneously print its input line:
echo ab | LC_CTYPE=ja_JP.eucjp grep -Fw b
[Bug#38223 introduced in grep 2.28]
The exit status of 'grep -L' is no longer incorrect when standard
output is /dev/null.
[Bug#37716 introduced in grep 3.2]
A performance bug has been fixed when grep is given many patterns,
each with no back-reference.
[Bug#33249 introduced in grep 2.5]
A performance bug has been fixed for patterns like '01.2' that
cause grep to reorder tokens internally.
[Bug#34951 introduced in grep 3.2]
** Build-related
The build procedure no longer relies on any already-built src/grep
that might be absent or broken. Instead, it uses the system 'grep'
to bootstrap, and uses src/grep only to test the build. On Solaris
/usr/bin/grep is broken, but you can install GNU or XPG4 'grep' from
the standard Solaris distribution before building GNU Grep yourself.
[bug introduced in grep 2.8]
Here's a snap release to fix a regression introduced in grep-3.2.
See the NEWS below for details:
Here are the compressed sources and a GPG detached signature[*]:
https://ftp.gnu.org/gnu/grep/grep-3.3.tar.xz
https://ftp.gnu.org/gnu/grep/grep-3.3.tar.xz.sig
Use a mirror for higher download bandwidth:
https://ftpmirror.gnu.org/grep/grep-3.3.tar.xz
https://ftpmirror.gnu.org/grep/grep-3.3.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-3.3.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.197-b8fd7
Automake 1.16a
Gnulib v0.1-2302-g5d6a3cdd5
NEWS
* Noteworthy changes in release 3.3 (2018-12-20) [stable]
** Bug fixes
Some uses of \b in the C locale and with the DFA matcher would fail, e.g.,
the following would print nothing (it should print the input line):
echo 123-x|LC_ALL=C grep '.\bx'
Using a multibyte locale, using certain regexp constructs (some ranges,
backreferences), or forcing use of the PCRE matcher via --perl-regexp (-P)
would avoid the bug.
[bug introduced in grep 3.2]
This is to announce grep-3.2, a stable release.
There have been 55 commits by 6 people in the 77 weeks since 3.1.
[note also the 867 gnulib-related changes]
See the NEWS below for a brief summary.
Thanks to everyone who has contributed. Special thanks to Paul Eggert for
so much help and to Norihiro Tanaka for the impressive dfa.c improvements.
The following people contributed changes to this release:
Barret Rhoden (1)
Bernhard Voelker (1)
Bruno Haible (2)
Jim Meyering (22)
Paul Eggert (28)
Stephan T. Lavavej (1)
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=v3.2
or run this command from a git-cloned grep directory:
git shortlog v3.1..v3.2
To summarize the 867 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v3.2
git submodule summary v3.1
==================================================================
Here are the compressed sources and a GPG detached signature[*]:
https://ftp.gnu.org/gnu/grep/grep-3.2.tar.xz
https://ftp.gnu.org/gnu/grep/grep-3.2.tar.xz.sig
Use a mirror for higher download bandwidth:
https://ftpmirror.gnu.org/grep/grep-3.2.tar.xz
https://ftpmirror.gnu.org/grep/grep-3.2.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-3.2.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.197-b8fd7
Automake 1.16a
Gnulib v0.1-2296-g453f37e2b
==================================================================
NEWS
* Noteworthy changes in release 3.2 (2018-12-20) [stable]
** Changes in behavior
The --files-without-match (-L) option now causes grep to succeed
when a file is listed, instead of when a line is selected. This
resembles what git-grep does.
** Bug fixes
The --recursive (-r) option no longer fails on MS-Windows.
[bug introduced in grep 2.11]
** Improvements
An over-30x performance improvement when many 'or'd expressions
share a common prefix, thanks to improvements in gnulib's dfa.c,
by Norihiro Tanaka. See gnulib commits v0.1-2110-ge648401be,
v0.1-2111-g4299106ce, v0.1-2117-g617a60974
An additional 3-23% speed-up when searching large files, via
increased initial buffer size.
grep now diagnoses stack overflow. Before grep-2.6, the included
regexp code would detect it. Since 2.6, grep defaulted to using
glibc's regexp, which lost that capability.
This release comes with a nice improvement for many:
grep '[0-9]' can be around 7 times faster in the multibyte
locales that most people use. Thank you, Paul Eggert.
There have been 27 commits by 4 people in the 20 weeks since 3.0.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Eric Blake (1)
Jim Meyering (17)
Juan Manuel Guerrero (1)
Paul Eggert (8)
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=v3.1
or run this command from a git-cloned grep directory:
git shortlog v3.0..v3.1
To summarize the 283 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v3.1
git submodule summary v3.0
==================================================================
Here are the compressed sources and a GPG detached signature[*]:
https://ftp.gnu.org/gnu/grep/grep-3.1.tar.xz
https://ftp.gnu.org/gnu/grep/grep-3.1.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-3.1.tar.xz
http://ftpmirror.gnu.org/grep/grep-3.1.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-3.1.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.185-b502e
Automake 1.99a
Gnulib v0.1-1429-g9ae75d145
==================================================================
NEWS
* Noteworthy changes in release 3.1 (2017-07-02) [stable]
** Improvements
grep '[0-9]' is now just as fast as grep '[[:digit:]]' when run
in a multi-byte locale. Before, it was several times slower.
** Changes in behavior
Context no longer excludes selected lines omitted because of -m.
For example, 'grep "^" -m1 -A1' now outputs the first two input
lines, not just the first line. This fixes a glitch that has been
present since -m was added in grep 2.5.
The following changes affect only MS-Windows platforms. First, the
--binary (-U) option now governs whether binary I/O is used, instead
of a heuristic that was sometimes incorrect. Second, the
--unix-byte-offsets (-u) option now has no effect on MS-Windows too.
This is to announce grep-3.0, a stable release.
Why so soon after 2.28? Because 2.28 introduced a pretty serious bug.
Why call it 3.0? Mostly because I felt like it.
There have been 4 commits by 2 people in the 3 days since 2.28.
Thanks to Paul Eggert for both of the nontrivial commits.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (2)
Paul Eggert (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=v3.0
or run this command from a git-cloned grep directory:
git shortlog v2.28..v3.0
To summarize the -2 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v3.0
git submodule summary v2.28
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-3.0.tar.xz
http://ftp.gnu.org/gnu/grep/grep-3.0.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-3.0.tar.xz
http://ftpmirror.gnu.org/grep/grep-3.0.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-3.0.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.185-b502e
Automake 1.99a
Gnulib v0.1-1146-gb6acb8d
NEWS
* Noteworthy changes in release 3.0 (2017-02-09) [stable]
** Bug fixes
grep without -F no longer goes awry when given two or more patterns
that contain no special characters other than '\' and also contain a
subpattern like '\.' that escapes a character to make it ordinary.
[bug introduced in grep 2.28]
grep no longer fails to build on PCRE versions before 8.20.
[bug introduced in grep 2.28]
This is to announce grep-2.28, a stable release.
Thank you especially to Paul Eggert and Norihiro Tanaka for all
of their improvements, both in the grep repository and via gnulib.
There have been 52 commits by 5 people in the 9 weeks since 2.27.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Arnold D. Robbins (1)
Jim Meyering (11)
Norihiro Tanaka (2)
Paul Eggert (33)
Zev Weiss (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.28
or run this command from a git-cloned grep directory:
git shortlog v2.27..v2.28
To summarize the 151 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v2.28
git submodule summary v2.27
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-2.28.tar.xz
http://ftp.gnu.org/gnu/grep/grep-2.28.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-2.28.tar.xz
http://ftpmirror.gnu.org/grep/grep-2.28.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.28.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.185-b502e
Automake 1.99a
Gnulib v0.1-1146-gb6acb8d
NEWS
* Noteworthy changes in release 2.28 (2017-02-06) [stable]
** Bug fixes
When grep -Fo finds matches of differing length, it could
mistakenly print a shorter one. Now it prints a longest one.
[bug introduced in grep-2.26]
When standard output is /dev/null, grep no longer fails when
standard input is a file in the Linux /proc file system, or when
standard input is a pipe and standard output is in append mode.
[bugs introduced in grep-2.27]
Fix performance regression with multiple patterns, e.g., for -Fi in
a multi-byte locale, or for -Fw in a single-byte locale.
[bugs introduced in grep-2.19, grep-2.22 and grep-2.26]
** Improvements
Improve performance for -E or -G pattern lists that are easily
converted to -F format.
This is to announce grep-2.27, a stable release.
There have been 40 commits by 4 people in the 9 weeks since 2.26.
Note that there were many additional important changes via gnulib.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (11)
Mark Veltzer (2)
Paul Eggert (26)
Zev Weiss (1)
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.27
or run this command from a git-cloned grep directory:
git shortlog v2.26..v2.27
To summarize the 98 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v2.27
git submodule summary v2.26
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-2.27.tar.xz
http://ftp.gnu.org/gnu/grep/grep-2.27.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-2.27.tar.xz
http://ftpmirror.gnu.org/grep/grep-2.27.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.27.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.171-527f1
Automake 1.99a
Gnulib v0.1-995-gca3ca77
NEWS
* Noteworthy changes in release 2.27 (2016-12-06) [stable]
** Bug fixes
grep no longer reports a false match in a multibyte, non-UTF8 locale
like zh_CN.gb18030, with a regular expression like ".*7" that just
happens to match the 4-byte representation of gb18030's \uC9, the
final byte of which is the digit "7".
[bug introduced in grep-2.19]
grep by default now reads all of standard input if it is a pipe,
even if this cannot affect grep's output or exit status. This works
better with nonportable scripts that run "PROGRAM | grep PATTERN
>/dev/null" where PROGRAM dies when writing into a broken pipe.
[bug introduced in grep-2.26]
grep no longer mishandles ranges in nontrivial unibyte locales.
[bug introduced in grep-2.26]
grep -P no longer attempts multiline matches. This works more
intuitively with unusual patterns, and means that grep -Pz no longer
rejects patterns containing ^ and $ and works when combined with -x.
[bugs introduced in grep-2.23] A downside is that grep -P is now
significantly slower, albeit typically still faster than pcregrep.
grep -m0 -L PAT FILE now outputs "FILE". [bug introduced in grep-2.5]
To output ':' and tab-align the following character C, grep -T no
longer outputs tab-backspace-':'-C, an approach that has problems if
run inside an Emacs shell window. [bug introduced in grep-2.5.2]
grep -T now uses worst-case widths of line numbers and byte offsets
instead of guessing widths that might not work with larger files.
[bug introduced in grep-2.5.2]
grep's use of getprogname no longer causes a build failure on HP-UX.
** Improvements
grep no longer reads the input in a few more cases when it is easy
to see that matching cannot succeed, e.g., 'grep -f /dev/null'.
This is to announce grep-2.26, a stable release.
There have been 110 commits by 5 people in the 23 weeks since 2.25.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed (both code and testing)!
The following people contributed code changes to this release:
Arnold Robbins (1)
Jim Meyering (29)
Norihiro Tanaka (23)
Paul Eggert (43)
Zev Weiss (14)
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.26
or run this command from a git-cloned grep directory:
git shortlog v2.25..v2.26
To summarize the 145 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v2.26
git submodule summary v2.25
==================================================================
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-2.26.tar.xz
http://ftp.gnu.org/gnu/grep/grep-2.26.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-2.26.tar.xz
http://ftpmirror.gnu.org/grep/grep-2.26.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.26.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.168-2b48
Automake 1.99a
Gnulib v0.1-897-g65e6915
==================================================================
NEWS
* Noteworthy changes in release 2.26 (2016-10-02) [stable]
** Bug fixes
Grep no longer omits output merely because it follows an output line
suppressed due to encoding errors. [bug introduced in grep-2.21]
In the Shift_JIS locale, grep no longer mistakenly matches in the
middle of a multibyte character. [bug present since "the beginning"]
** Improvements
grep can be much faster now when standard output is /dev/null.
grep -F is now typically much faster when many patterns are given,
as it now uses the Aho-Corasick algorithm instead of the
Commentz-Walter algorithm in that case.
grep -iF is typically much faster in a multibyte locale, if the
pattern and its case counterparts contain only single byte characters.
grep with complicated expressions (e.g., back-references) and without
-i now uses the regex fastmap for better performance.
In multibyte locales, grep now handles leading "." in patterns more
efficiently.
grep now prints a "FILENAME:LINENO: " prefix when diagnosing an
invalid regular expression that was read from an '-f'-specified file.
This is to announce grep-2.25, a stable release.
Yet another bug-fix release. This one was prompted
primarily by the realization that even with LC_ALL=C,
grep-2.24 could still report "Binary file F matches".
Special thanks to Paul Eggert for doing so much of
the work, and to Assaf Gordon for his patch to make
grep diagnose errors more precisely.
There have been 15 commits by 2 people in the 6 weeks since 2.24.
See the NEWS below for a brief summary.
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.25
or run this command from a git-cloned grep directory:
git shortlog v2.24..v2.25
To summarize the 55 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v2.25
git submodule summary v2.24
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-2.25.tar.xz
http://ftp.gnu.org/gnu/grep/grep-2.25.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-2.25.tar.xz
http://ftpmirror.gnu.org/grep/grep-2.25.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.25.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.147-5ad35
Automake 1.99a
Gnulib v0.1-752-gb7bc3c1
NEWS
* Noteworthy changes in release 2.25 (2016-04-21) [stable]
** Bug fixes
In the C or POSIX locale, grep now treats all bytes as valid
characters even if the C runtime library says otherwise. The
revised behavior is more compatible with the original intent of
POSIX, and the next release of POSIX will likely make this official.
[bug introduced in grep-2.23]
grep -Pz no longer mistakenly diagnoses patterns like [^a] that use
negated character classes. [bug introduced in grep-2.24]
grep -oz now uses null bytes, not newlines, to terminate output lines.
[bug introduced in grep-2.5]
** Improvements
grep now outputs details more consistently when reporting a write error.
E.g., "grep: write error: No space left on device" rather than just
"grep: write error".
This is to announce grep-2.24, a stable bug-fix-only release.
This release, so soon after 2.23, was prompted by the discovery
of two bugs related to the --null-data (-z) option.
These bugs were introduced in 2010 and 2002 respectively.
There have been 8 commits by 2 people in the 5 weeks since 2.23.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (7)
Paul Eggert (1)
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.24
or run this command from a git-cloned grep directory:
git shortlog v2.23..v2.24
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-2.24.tar.xz
http://ftp.gnu.org/gnu/grep/grep-2.24.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-2.24.tar.xz
http://ftpmirror.gnu.org/grep/grep-2.24.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.24.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.147-5ad35
Automake 1.99a
Gnulib v0.1-697-gcd6a452
==================================================================
NEWS
* Noteworthy changes in release 2.24 (2016-03-10) [stable]
** Bug fixes
grep -z would match strings it should not. To trigger the bug, you'd
have to use a regular expression including an anchor (^ or $) and a
feature like a range or a backreference, causing grep to forego its DFA
matcher and resort to using re_search. With a multibyte locale, that
matcher could mistakenly match a string containing a newline.
For example, this command:
printf 'a\nb\0' | LC_ALL=en_US.utf-8 grep -z '^[a-b]*b'
would mistakenly match and print all four input bytes. After the fix,
there is no match, as expected.
[bug introduced in grep-2.7]
grep -Pz now diagnoses attempts to use patterns containing ^ and $,
instead of mishandling these patterns. This problem seems to be
inherent to the PCRE API; removing this limitation is on PCRE's
maint/README wish list. Patterns can continue to match literal ^
and $ by escaping them with \ (now needed even inside [...]).
[bug introduced in grep-2.5]
This is to announce grep-2.23, a stable bug-fix-only release.
Special thanks to Paul Eggert who did nearly all of the heavy
lifting for this release.
There have been 35 commits by 2 people in the 14 weeks since 2.22.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (14)
Paul Eggert (21)
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.23
or run this command from a git-cloned grep directory:
git shortlog v2.22..v2.23
To summarize the 91 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v2.23
git submodule summary v2.22
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-2.23.tar.xz
http://ftp.gnu.org/gnu/grep/grep-2.23.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-2.23.tar.xz
http://ftpmirror.gnu.org/grep/grep-2.23.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.23.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.147-5ad35
Automake 1.99a
Gnulib v0.1-697-gcd6a452
==================================================================
NEWS
* Noteworthy changes in release 2.23 (2016-02-04) [stable]
** Bug fixes
Binary files are now less likely to generate diagnostics and more
likely to yield text matches. grep now reports "Binary file FOO
matches" and suppresses further output instead of outputting a line
containing an encoding error; hence grep can now report matching text
before a later binary match. Formerly, grep reported FOO to be
binary when it found an encoding error in FOO before generating
output for FOO, which meant it never reported both matching text and
matching binary data; this was less useful for searching text
containing encoding errors in non-matching lines.
[bug introduced in grep-2.21]
grep -c no longer stops counting when finding binary data.
[bug introduced in grep-2.21]
grep no longer outputs encoding errors in unibyte locales.
For example, if the byte '\x81' is not a valid character in a
unibyte locale, grep treats the byte as binary data.
[bug introduced in grep-2.21]
grep -oP is no longer susceptible to an infinite loop when processing
invalid UTF8 just before a match.
[bug introduced in grep-2.22]
--exclude and related options are now matched against trailing
parts of command-line arguments, not against the entire arguments.
This partly reverts the --exclude-related change in 2.22.
[bug introduced in grep-2.22]
--line-buffer is no longer ineffective when combined with -l.
[bug introduced in grep-2.5]
-xw is now equivalent to -x more consistently, with -P and with backrefs.
[bug only partially fixed in grep-2.19]
This is to announce grep-2.22, a stable release.
Special thanks to Norihiro Tanaka and Paul Eggert
for making so many fine changes.
There have been 86 commits by 6 people in the 49 weeks since 2.21.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (34)
Norihiro Tanaka (17)
Paul Eggert (32)
Santiago Ruano Rincón (1)
Yuliy Pisetsky (1)
Zev Weiss (1)
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.22
or run this command from a git-cloned grep directory:
git shortlog v2.21..v2.22
To summarize the 344 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v2.22
git submodule summary v2.21
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-2.22.tar.xz
http://ftp.gnu.org/gnu/grep/grep-2.22.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-2.22.tar.xz
http://ftpmirror.gnu.org/grep/grep-2.22.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.22.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.147-5ad35
Automake 1.99a
Gnulib v0.1-606-g956fa54
==================================================================
NEWS
* Noteworthy changes in release 2.22 (2015-11-01) [stable]
** Improvements
Performance has improved for patterns containing very long strings,
reducing preprocessing time for an N-byte regexp from O(N^2) to
only slightly superlinear for most patterns. Before, a command like
the following would take over a minute, but now, it takes less than
a second:
: | grep -f <(seq -s '' 99999)
When building grep, 'configure' now uses PCRE's pkg-config module for
configuration information, rather than attempting to guess it by hand.
** Bug fixes
A DFA matcher bug made this command mistakenly print its input line:
echo axb | grep -E '^x|x$'
Likewise for this equivalent command:
echo axb | grep -e '^x' -e 'x$'
[bug introduced in grep-2.19 ]
grep no longer reads from uninitialized memory or from beyond the end
of the heap-allocated input buffer. This fix addressed CVE-2015-1345.
[bug introduced in grep-2.19 ]
With -z, '.' and '[^x]' in a pattern now consistently match newline.
Previously, they sometimes matched newline, and sometimes did not.
[bug introduced in grep-2.4]
When the JIT stack is exhausted, grep -P now grows the stack rather
than reporting an internal PCRE error.
'grep -D skip PATTERN FILE' no longer hangs if FILE is a fifo.
[bug introduced in grep-2.12]
--exclude and related options are now matched against entire
command-line arguments, not against command-line components.
[bug introduced in grep-2.6]
Fix performance degradation of grep -Fw in unibyte locales.
[bug introduced in grep-2.19 ]
This is to announce grep-2.21, a stable release.
There have been 94 commits by 3 people in the 25 weeks since 2.20.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Jim Meyering (26)
Norihiro Tanaka (17)
Paul Eggert (51)
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.21
or run this command from a git-cloned grep directory:
git shortlog v2.20..v2.21
To summarize the 123 gnulib-related changes, run these commands
from a git-cloned grep directory:
git checkout v2.21
git submodule summary v2.20
Here are the compressed sources and a GPG detached signature[*]:
http://ftp.gnu.org/gnu/grep/grep-2.21.tar.xz
http://ftp.gnu.org/gnu/grep/grep-2.21.tar.xz.sig
Use a mirror for higher download bandwidth:
http://ftpmirror.gnu.org/grep/grep-2.21.tar.xz
http://ftpmirror.gnu.org/grep/grep-2.21.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.21.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.117-1717
Automake 1.99a
Gnulib v0.1-262-g46d015f
==================================================================
NEWS
* Noteworthy changes in release 2.21 (2014-11-23) [stable]
** Improvements
Performance has been greatly improved for searching files containing
holes, on platforms where lseek's SEEK_DATA flag works efficiently.
Performance has improved for rejecting data that cannot match even
the first part of a nontrivial pattern.
Performance has improved for very long strings in patterns.
If a file contains data improperly encoded for the current locale,
and this is discovered before any of the file's contents are output,
grep now treats the file as binary.
grep -P no longer reports an error and exits when given invalid UTF-8 data.
Instead, it considers the data to be non-matching.
** Bug fixes
grep no longer mishandles patterns that contain \w or \W in multibyte
locales.
grep would fail to count newlines internally when operating in non-UTF8
multibyte locales, leading it to print potentially many lines that did
not match. E.g., the command, "seq 10 | env LC_ALL=zh_CN src/grep -n .."
would print this:
1:1
2
3
4
5
6
7
8
9
10
implying that the match, "10" was on line 1.
[bug introduced in grep-2.19]
grep -F -x -o no longer prints an extra newline for each match.
[bug introduced in grep-2.19]
grep in a non-UTF8 multibyte locale could mistakenly match in the middle
of a multibyte character when using a '^'-anchored alternate in a pattern,
leading it to print non-matching lines. [bug present since "the beginning"]
grep -F Y no longer fails to match in non-UTF8 multibyte locales like
Shift-JIS, when the input contains a 2-byte character, XY, followed by
the single-byte search pattern, Y. grep would find the first, middle-
of-multibyte matching "Y", and then mistakenly advance an internal
pointer one byte too far, skipping over the target "Y" just after that.
[bug introduced in grep-2.19]
grep -E rejected unmatched ')', instead of treating it like '\)'.
[bug present since "the beginning"]
On NetBSD, grep -r no longer reports "Inappropriate file type or format"
when refusing to follow a symbolic link.
[bug introduced in grep-2.12]
** Changes in behavior
The GREP_OPTIONS environment variable is now obsolescent, and grep
now warns if it is used. Please use an alias or script instead.
In locales with multibyte character encodings other than UTF-8,
grep -P now reports an error and exits instead of misbehaving.
When searching binary data, grep now may treat non-text bytes as
line terminators. This can boost performance significantly.
grep -z no longer automatically treats the byte '\200' as binary data.