On Tue, Oct 27, 2015 at 2:47 PM, Jeff King <peff@xxxxxxxx> wrote: > On Tue, Oct 27, 2015 at 10:52:52AM -0700, Junio C Hamano wrote: >> Yes. Probably the right way forward is to make it a non-issue by >> teaching users how to control the lifetime of the "daemon" process, >> and wean them off relying on "it is auto-spawned if you forgot to >> start", as that convenience of auto-spawning is associated with >> "...but how it is auto-shutdown really depends on many things in >> your specific environment", which is the issue. > > I dunno. I think the auto-spawn is really what makes it usable; you can > drop it in with "git config credential.helper config" and forget about > it. Anything more fancy requires touching your login/startup files. > Certainly I'm not opposed to people setting it up outside of the > auto-spawn, but I wouldn't want that feature to go away. Perhaps we could express the auto-spawn more explicitly, something like "git config credential.pre-helper start-cache-daemon". A way to run a command before the credential helpers start would be useful to our magit workaround for this issue (currently we start the daemon before "push", "fetch", and "pull", but it won't work with user aliases that run those commands). > > I am a little surprised that credential-cache gets wide use. I would > think most people would prefer to use a system-specific secure-storage > helper. I don't know what the state of the art is for that on Linux[1], but > we seem to have only gnome-keyring in contrib/. I'm not sure it's that widely used. Perhaps most people use ssh-agent? That's what I do, though I've been experimenting with credential-cache since it was brought up by a magit user. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html