rust/ripgrep
1
0
Fork 0
mirror of https://github.com/BurntSushi/ripgrep.git synced 2024-12-12 19:18:24 +02:00
Code Issues Releases Activity

changelog: a bit of polish

Browse Source 
I think I'm just waiting on the CVE to be published at this point.
This commit is contained in:
Andrew Gallant 2021-06-01 06:59:06 -04:00
parent 6e27649af1
commit 079a23b515
No known key found for this signature in database
GPG Key ID: B2E3A4923F8B0D44
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
CHANGELOG.md
View File

@ -8,10 +8,15 @@ some performance improvements and some minor breaking changes.
A new short flag, `-.`, has been added. It is an alias for the `--hidden` flag, A new short flag, `-.`, has been added. It is an alias for the `--hidden` flag,
which instructs ripgrep to search hidden files and directories. which instructs ripgrep to search hidden files and directories.
ripgrep is also used a new ripgrep is nowing using a new
[vectorized implementation of `memmem`](https://github.com/BurntSushi/memchr/pull/82), [vectorized implementation of `memmem`](https://github.com/BurntSushi/memchr/pull/82),
which is used to accelerate many common searches. If you notice any performance which accelerates many common searches. If you notice any performance
regressions (or major improvements), I'd love to hear about them. regressions (or major improvements), I'd love to hear about them through an
issue report!
Also, for Windows users targeting MSVC, Cargo will now build fully static
executables of ripgrep. The release binaries for ripgrep 13 have been compiled
using this configuration.
**BREAKING CHANGES**: **BREAKING CHANGES**:
@ -44,6 +49,8 @@ would produce outright incorrect counts. Another alternative would be to simply
count the number of lines---even if it's more than the number of matches---but count the number of lines---even if it's more than the number of matches---but
that seems highly unintuitive. that seems highly unintuitive.
**FULL LIST OF FIXES AND IMPROVEMENTS:**
Security fixes: Security fixes:
* [CVE-2021-3013](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3013): * [CVE-2021-3013](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3013):