Duy Nguyen [off-list ref] writes:
I was wrong, GIT_WORK_TREE support was added in git-clone many years
ago in 20ccef4 (make git-clone GIT_WORK_TREE aware - 2007-07-06). So
my change accidentally triggers an (undocumented) feature. We could
add a hack to ignore GIT_WORK_TREE if GIT_DIR is set too, but I don't
think people will like it. I don't really like reverting d95138e
(setup: set env $GIT_WORK_TREE when work tree is set, like $GIT_DIR -
2015-06-26) because another bug reappears.
So I'm out of options..
Perhaps d95138e can be reverted and then the bug it tried to fix can
be fixed in a different way somehow?
(I am not quite up to speed yet, so the above may turn out to be
infeasible--take it with a large grain of salt please).