git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Devin Lehmacher <djl329@cornell.edu>
Cc: Noam Postavsky <npostavs@users.sourceforge.net>,
	Jonathan Nieder <jrnieder@gmail.com>, <git@vger.kernel.org>
Subject: Re: [GSoC] Move ~/.git-credential-cache to ~/.cache/git
Date: Fri, 10 Mar 2017 19:17:04 -0800	[thread overview]
Message-ID: <xmqqinngwlhr.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <3B988055-D8A3-43B7-BF5F-C43479EF7BEB@cornell.edu> (Devin Lehmacher's message of "Fri, 10 Mar 2017 21:27:23 -0500")

Devin Lehmacher <djl329@cornell.edu> writes:

> If I’m not mistaken magit won’t stop working with the changed
> location since it will just spawn an new instance of the
> daemon. The only downside would be it wouldn’t get credentials
> that were cached in the default socket.

I am not quite sure how you can say "only" in that sentence.  Isn't
the whole point of socket based daemon interface to allow starting
the daemon so that it can keep using it?

Somebody upthread mentioned checking the current location (and use
it if there is) and then use the new location, which I found a more
reasonable approach.

Assuming that it is sensible to move it from ~/.git-credential-cache
to ~/.cache/git/ in the first place, that is.  If both are equally
acceptable places, then perhaps a configuration that allows those
who want to have things in ~/.config/git/ to specify where to have
the thing (and those without such a custom configuration will keep
using the current location) may be more appropriate.

      reply	other threads:[~2017-03-11  3:17 UTC|newest]

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

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqinngwlhr.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=djl329@cornell.edu \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).