2016-03-16 3:21 GMT+08:00 Jeff King <p...@peff.net>: > I don't think so. I suppose one could have a script that tests for the > existence of the socket or something.
I agree, that is what I meant by "third-party tools". But for user who write script like that, it's easy to figure out the problem and either update his/her scripts or explicitly declare the path of the socket in his gitconfig. Anyway, most users will not be affected. > But then, I don't think "use the > old directory if it exists" really solves that. Such a script would work > on people who had already run the old version of credential-cache, and > break on new ones. If back-compatibility must be ensured, the only graceful solution I can image is a new option entry like `xdg-style-path` being added to gitconfig and default it to false. I doubt whether the increasing complexity is worthy just for the back-compatibilty of a socket path. -- 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
