I don’t understand the comment, “In the example env, the bash prereq is appended not pretended to your path.”.
The release note indicates that the specific prereq versions of bash and perl must be installed into the same directory as the git installation directory, and then that directory prepended to PATH. This will put the prereq version of bash on your path. Am I missing something?
Regarding GIT_SHELL: I’m not sure what that’s actually used for. I’ll have to check with the primary developer and get back to you.
We plan to iron out some of these issues over time, but it’s a fairly complex problem. The goal is to have a complete set of open source tools that fully implement enhanced ASCII support, so that users can always run with _BPXK_AUTOCVT=ON and work seamlessly in a mixed ASCII/EBCDIC environment. For many tools this is straightforward, but there are often complications when tools pipe their output to other tools (which happens a lot with git, both internally and when used in scripts).
The way I currently tend to work with git is to have a separate shell running that I use for git commands, and do all my other work in shells that do not have git and its prereqs on PATH. This can be done either with multiple login windows or (as I do) with multiple shell buffers in emacs.