Re: git diff --exit-code misbehaving in 2.46.x

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 25.09.24 um 16:27 schrieb Jan Wendland:
> Hey team,
>
> git diff --exit-code in 2.46.x is unexpectedly returning a zero exit
> code for files marked as binary in .gitattributes where 2.45.x would
> correctly produce a non-zero exit code.
>
> To reproduce:
> mkdir -p git-exit-code/dist
> cd git-exit-code
> git init
> echo "hi" > dist/main.js
> echo "dist/** binary" > .gitattributes
> git add --all
> git commit -m "Initial commit"
> echo "some change" >> dist/main.js
> git diff --exit-code
> echo $? # actual is 0, expected to be 1
>
> Is this intended?

Thanks for the report!  This is a known bug.  The "next" branch contains
a fix, 9a41735af6 (diff: report modified binary files as changes in
builtin_diff(), 2024-09-21).

René






[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux