Ingo BrÃckl wrote: > The tests after '--set in alternative GIT_CONFIG' failed because > variable GIT_CONFIG was still set. [...] > Is it only me (bash 3.2.48(1)-release) experiencing these failures? Could you explain the nature of the failures in more detail? What version of git are you building? Is GIT_CONFIG already set in the environment before you run t1300-repo-config.sh (it shouldn't matter)? How does output from "sh t1300-repo-config.sh -v -i" end? If that doesn't end up being helpful, how about "GIT_TRACE=1 sh -x t1300-repo-config.sh -v -i"? Regards, Jonathan -- 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