Ref T10832. In practice, git --version is not a useful test for this issue:
- Vendors like Debian have backported the patch into custom versions like 0.0.0.1-debian-lots-of-patches.3232.
- Vendors like Ubuntu distribute multiple different versions which report the same string from git --version, some of which are patched and some of which are not.
In other cases, we can perform an empirical test for the vulnerability. Here, we can not, because we can't write a 2GB path in a reasonable amount of time.
Since vendors (other than Apple) generally seem to be on top of this and any warning we try to raise based on git --version will frequently be incorrect, don't raise this warning.
I'll note this in the changelog instead.