As of git 1.8.1.1 and above (tested up to 1.8.1.3), if the home directory can't be accessed, it results in a fatal error. In git 1.8.1 and below this same setup just resulted in warnings. Was this an intentional change?
I ran into this in a situation where sudo is being used to execute a script as root and then git ends up getting executed as a different user. In this case HOME ends up being /root when git is called as this different user. This home value is obviously incorrect, so there's an issue there, but it would be perhaps be nice if this still just resulted in warnings. Here's a simple way to reproduce if run as a non-root user: git 1.8.1.1 (fatal error, doesn't work): $ env HOME=/root git ls-remote http://github.com/sstephenson/rbenv.git v0.4.0 fatal: unable to access '/root/.config/git/config': Permission denied git 1.8.1 (warnings, but still works): $ env HOME=/root git ls-remote http://github.com/sstephenson/rbenv.git v0.4.0 warning: unable to access '/root/.config/git/config': Permission denied warning: unable to access '/root/.gitconfig': Permission denied warning: unable to access '/root/.config/git/config': Permission denied warning: unable to access '/root/.gitconfig': Permission denied warning: unable to access '/root/.config/git/config': Permission denied warning: unable to access '/root/.gitconfig': Permission denied warning: unable to access '/root/.config/git/config': Permission denied warning: unable to access '/root/.gitconfig': Permission denied 9375e99f921f428849f19efe2a2e500b3295d1a7 refs/tags/v0.4.0 Thanks, Nick -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
