You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2021. It is now read-only.
Recently in v3.5 (November 2020?) GNU grep made the following change
"The message that a binary file matches is now sent to standard error". This causes 16 tests to fail, since they run "grep SOMTHING log.s2c | wc -l" and log.s2c is considered a binary file.
In Debian (1) I proposed using "grep -c" instead, as this seems to have the desired behavior on binary files. I'm not sure this is the best approach in general. Alternatives include
redirecting standard error
running grep with the "-a" option (not sure how portable that is).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Recently in v3.5 (November 2020?) GNU grep made the following change
"The message that a binary file matches is now sent to standard error". This causes 16 tests to fail, since they run "grep SOMTHING log.s2c | wc -l" and log.s2c is considered a binary file.
In Debian (1) I proposed using "grep -c" instead, as this seems to have the desired behavior on binary files. I'm not sure this is the best approach in general. Alternatives include
The text was updated successfully, but these errors were encountered: