Merge branch 'ma/diff-doc-clarify-regexp-example'
Doc clarification. * ma/diff-doc-clarify-regexp-example: diff-options.txt: avoid "regex" overload in examplemaint
commit
0d114107f5
|
|
@ -567,13 +567,13 @@ To illustrate the difference between `-S<regex> --pickaxe-regex` and
|
||||||
file:
|
file:
|
||||||
+
|
+
|
||||||
----
|
----
|
||||||
+ return !regexec(regexp, two->ptr, 1, ®match, 0);
|
+ return frotz(nitfol, two->ptr, 1, 0);
|
||||||
...
|
...
|
||||||
- hit = !regexec(regexp, mf2.ptr, 1, ®match, 0);
|
- hit = frotz(nitfol, mf2.ptr, 1, 0);
|
||||||
----
|
----
|
||||||
+
|
+
|
||||||
While `git log -G"regexec\(regexp"` will show this commit, `git log
|
While `git log -G"frotz\(nitfol"` will show this commit, `git log
|
||||||
-S"regexec\(regexp" --pickaxe-regex` will not (because the number of
|
-S"frotz\(nitfol" --pickaxe-regex` will not (because the number of
|
||||||
occurrences of that string did not change).
|
occurrences of that string did not change).
|
||||||
+
|
+
|
||||||
Unless `--text` is supplied patches of binary files without a textconv
|
Unless `--text` is supplied patches of binary files without a textconv
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue