Hi,
I happen to have quite large binary files in my repos.
Today I realized that a line like
git log -G a
searches also files found to be binary (or explicitly marked as binary).
Is that on purpose?
The documentation of "-G<regex>" states
"Look for differences whose patch text contains added/removed lines that
match <regex>."
which contradicts the current behaviour. At least for me text != binary.
To reproduce:
$ git init
$ echo -e "a\0b" > data.bin
$ git add data.bin
$ git commit -m "Add new data"
$ git log -p
[...]
diff --git a/data.bin b/data.bin
new file mode 100644
index 0000000..1a23e4b
Binary files /dev/null and b/data.bin differ
$ git log -G a
[...]
Add new data
I've verified the behaviour with git version 2.12.0.windows.1 and git
version 2.12.0.189.g3bc5322 on debian.
If it is on purpose is there a config option to disable that?
Thanks for reading,
Thomas
