On Tue, Mar 15, 2016 at 05:48:18AM +0000, 惠轶群 wrote: > On Tue, Mar 15, 2016, 11:13 AM Jeff King <peff@xxxxxxxx> wrote: > > The socket is inherently ephemeral, and designed to go > > away after a few minutes (and the program designed to run sanely when it > > does not exist). > > I agree. > > > So yes, when you switch from older git to newer git, you might > > technically have a cache-daemon running that you _could_ contact, but > > don't find it. But I don't think it's a big deal in practice, and not > > worth designing around > > Yes, it's OK with git itself. What I worry about is that this change break > some third-party tools. Does it matter? I don't think so. I suppose one could have a script that tests for the existence of the socket or something. 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. -Peff -- 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