I've bisected git and it was commit 9d3f002f21f78576f3c31ae94ce78de54e305c95 that changed this behavior. This commit was released in v1.8.3 and is not present in v1.8.2.3. I'll update my patch to switch behavior based on the output of `git --version`; if <1.8.3 I'll trigger the workaround.
I've bisected git and it was commit 9d3f002f21f7857 6f3c31ae94ce78d e54e305c95 that changed this behavior. This commit was released in v1.8.3 and is not present in v1.8.2.3. I'll update my patch to switch behavior based on the output of `git --version`; if <1.8.3 I'll trigger the workaround.