All of lore.kernel.org
 help / color / mirror / Atom feed
From: Devin Lehmacher <djl329@cornell.edu>
To: <git@vger.kernel.org>
Subject: [GSoC] Move ~/.git-credential-cache to ~/.cache/git
Date: Fri, 10 Mar 2017 18:30:55 -0500	[thread overview]
Message-ID: <8BE1A361-32BB-4164-AD54-949555855C52@cornell.edu> (raw)

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

             reply	other threads:[~2017-03-10 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 23:30 Devin Lehmacher [this message]
2017-03-11  0:26 ` [GSoC] Move ~/.git-credential-cache to ~/.cache/git Jonathan Nieder
2017-03-11  1:02   ` Noam Postavsky
2017-03-11  2:27     ` Devin Lehmacher
2017-03-11  3:17       ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8BE1A361-32BB-4164-AD54-949555855C52@cornell.edu \
    --to=djl329@cornell.edu \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.