94da9193a6 ("grep: add support for PCRE v2", 2017-06-01) allocate
a stack and assign it to a match context, but never pass it to
pcre2_jit_match, using instead the default.
Signed-off-by: Carlo Marcelo Arenas Belón
---
This might have positive performance consequences (per the comments)
but haven
On Sun, Jul 21, 2019 at 2:31 PM Carlo Marcelo Arenas Belón
wrote:
> grep: skip UTF8 checks explicitally
s/explicitally/explicitly/
> Usually PCRE is compiled with JIT support, and therefore the code
> path used includes calling pcre2_jit_match (for PCRE2), that ignores
> invalid UTF-8 in the cor
Usually PCRE is compiled with JIT support, and therefore the code
path used includes calling pcre2_jit_match (for PCRE2), that ignores
invalid UTF-8 in the corpus.
Make that option explicit so it can be also used when JIT is not
enabled and pcre2_match is called instead, preventing `git grep`
to a
From: Sun Chao
When a packed ref is deleted, the whole packed-refs file is
rewrite and omit the ref that no longer exists. However if
another gc command is running and call `pack-refs --all`
simultaneously, there is a change that a ref just updated
will lost the newly commits.
Through these step
From: Sun Chao
When a packed ref is deleted, the whole packed-refs file is
rewrite and omit the ref that no longer exists. However if
another gc command is running and call `pack-refs --all`
simultaneously, there is a change that a ref just updated
will lost the newly commits.
There are two vali
Here is today's test coverage report. If anyone is interested, I now also have
a way to generate these reports based on a topic branch on any public Git repo.
Let me know if you would like me to run a build and give you the text report
directly. I've used it myself for work in progress before su
6 matches
Mail list logo
