Jeff King <peff@xxxxxxxx> writes: >> I can see how this works for "git -C ... rev-parse ..." or any other >> built-in commands, but I am not sure if this is sufficient when any >> non-built-in command is used in the perf framework. How does it >> interact with GIT_EXEC_PATH we set in ../test-lib.sh that is >> dot-sourced by ./perf-lib.sh that everybody dot-sources? > > I didn't test it but it should work because we are pointing to > bin-wrappers/git, which will override GIT_EXEC_PATH, and stick itself at > the front of the PATH. Ah, yes, bin-wrappers/git is not the real binary we just have built but overrides GIT_EXEC_PATH to point at the matching version. I forgot about that. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html