From: 惠轶群 <huiyiqun@gmail.com>
Date: Wed, 16 Mar 2016 10:45:42 GMT
Subject: Re: [GSOC] Microproject "Move ~/.git-credential-cache to ~/.config/git"
Message-ID: <CAKqreuxn7upMwOQH54rdA9nv1wCLNSSPjrWH3xejHP-ib+Ynuw@mail.gmail.com>
In-Reply-To: <20160315192154.GA30693@sigill.intra.peff.net>

2016-03-16 3:21 GMT+08:00 Jeff King <peff@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.