git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[GSoC] Move ~/.git-credential-cache to ~/.cache/git

From
DLDevin Lehmacher <djl329@cornell.edu>
Date
Mar 10, 2017, 23:30 UTC
Message-ID
<8BE1A361-32BB-4164-AD54-949555855C52@cornell.edu>
I started working on this microproject and am not quite sure what is necessary for backwards compatibility. Since the socket is recreated whenever the credential daemon exits backwards compatibility shouldn’t really be a concern with regard to where the socket is located in the filesystem.
However, contrib/persistent-https depends on the socket being at ~/.git-credential-cache/socket, so changing the default location would break this. However, if we need to keep the socket at that location for cases like this I don’t understand how this change would be helpful in any way.
Is it safe to change the default location for this socket and removing the original location?

Thanks in advanced, Devin Lehmacher

Next: Jonathan Nieder
Message 1 of 5 in “[GSoC] Move ~/.git-credential-cache to ~/.cache/git”
  1. Devin LehmacherMar 10, 2017
  2. Jonathan NiederMar 11, 2017
  3. Noam PostavskyMar 11, 2017
  4. Devin LehmacherMar 11, 2017
  5. Junio C HamanoMar 11, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.