Re: [PATCH/RFC/GSoC 3/3] t0301: test credential-cache support of XDG_RUNTIME_DIR
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 16, 2016, 17:24 UTC
- Message-ID
- <xmqqbn6e5o9v.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <CAKqreuwRpS3uP6=afm-0pBkPW0-bqoJconnKO5q3qTgZwdU_xQ@mail.gmail.com>
惠轶群 <huiyiqun@gmail.com> writes:
Show 6 quoted lines
>> Is it because the wish is to always use /tmp/git-$uid/ as a fallback >> for $XDG_RUNTIME_DIR (as opposed to ~/.git-credential-cache/, which >> is specific to the credential-cache and would look strange if we >> used it for other "runtime" things)? > > Yes, I mean to use it as a general fallback for git.
If that is the case the code probably needs to be a bit more careful before deciding to use /tmp/git-$uid/ directory (is it really $uid's? can anybody else write to it to race with the real user? etc.)
> On the other hand, I think, falling back to $HOME/.git-credential-cache/socket > doesn't make any sense for back-compability cannot be ensured.
What do you mean by that?
Using ~/.git-credential-cache/credential-cache.sock would not help at all for existing users, but ~/.git-credential-cache/socket would interoperate well with users with existing versions of Git, no?
>> Just being curious, and wanting to see the reasoning behind the >> design decision the patch series makes in the log message of one of >> these patches.