bug#63780: �ظ��� bug#63780: Reversing the grep message output type matching binary files (without the -a option added) changed from stdout to stderr

[2773414454]

 I know my suggestion may seem silly, but in fact, I 
used grep3.4 related code for my project and provided it to the client, and 
recently provided the client with grep3.7 for an upgrade. After upgrade I found 
that the change from grep3.4 to grep3.5 caused my project to become invalid.

 Since the project is running, my dilemma is that I can only 
modify the source code of grep3.7 to solve the customer problem, and I cannot 
adapt the grep command to the project. I tried to roll back the behavior to 
grep3.4. I find that there are batch use cases that fail. At least 3 grep 
binary matching open source patches need to be backed up, this is too much 
modification, and I am afraid of introducing new problems to affect the use of 
customers. So my original intention is to ask the community whether there is a 
better way to modify the grep3.7 source code. The binary matching behavior of 
grep3.7 and grep3.4 is consistent.

  I sincerely hope to get your help.



2773414454
2773414...@qq.com








----
??: 
   "Jim Meyering"   
 

bug#63780: Reversing the grep message output type matching binary files (without the -a option added) changed from stdout to stderr

[2773414454]

Hi !


Between grep3.4 and grep3.5, the grep message output type matching binary files 
(without the -a option added) changed from stdout to stderr. This results in 
the inability to pipe in matching messages, resulting in significant changes to 
the user experience. But this modification doesn't actually do much. Could you 
consider reversing this change?




2773414454
2773414...@qq.com