2018-02-22 - email@example.com
- Use %license (boo#1082318)
2017-07-03 - firstname.lastname@example.org
- Update to grep 3.1
* grep '[0-9]' is now just as fast as grep '[[:digit:]]' when run
in a multi-byte locale
* Context no longer excludes selected lines omitted because of -m
2017-06-01 - email@example.com
- Use https url's
- Drop no longer needed explicit pie
- Enable profiled build
2017-02-11 - firstname.lastname@example.org
- Update to version 3.0:
* 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.
* grep no longer fails to build on PCRE versions before 8.20.
- Cleanup spec file:
* Drop support for old distributions
* Create lang subpackage
* Use fdupes to replace duplicate files with symlinks
2017-02-08 - email@example.com
- Update to version 2.28:
* Improve performance for -E or -G pattern lists that are easily
converted to -F format.
* Fix performance regression with multiple patterns.
* 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.
* When grep -Fo finds matches of differing length, it could
mistakenly print a shorter one. Now it prints a longest one.
- Drop upstreamed proc-lseek-glitch.patch
2016-12-12 - firstname.lastname@example.org
- testsuite.patch: remove
- proc-lseek-glitch.patch: work around proc lseek glitch
2016-12-07 - email@example.com
- Update to grep 2.27
* 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".
* 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.
* grep no longer mishandles ranges in nontrivial unibyte locales.
* grep -P no longer attempts multiline matches.
* grep -m0 -L PAT FILE now outputs "FILE".
* 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.
* grep -T now uses worst-case widths of line numbers and byte offsets
instead of guessing widths that might not work with larger files.
* 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'.
2016-10-28 - firstname.lastname@example.org
- grep 2.26:
* no longer omit output merely because it follows an output line
suppressed due to encoding errors
* In the Shift_JIS locale, no longer mistakenly match in the
middle of a multibyte character
* 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
* 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
* grep now prints a "FILENAME:LINENO: " prefix when diagnosing
an invalid regular expression that was read from an
2016-04-22 - email@example.com
- grep 2.25:
* In the C or POSIX locale, grep now treats all bytes as valid
characters even if the C runtime library says otherwise.
( Fixes yast2-users and other build failures - boo#966780 )
* grep -oz now uses null bytes, not newlines, to terminate output
* grep now outputs details more consistently when reporting a