From 28fc8d491f3d6c0dd202eb525424a1557dbc06f7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 9 Sep 2022 12:30:46 -0400 Subject: [PATCH] comment --- ...t_1_ae15355f54b5137e696aaf5d2111806b._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_1_ae15355f54b5137e696aaf5d2111806b._comment diff --git a/doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_1_ae15355f54b5137e696aaf5d2111806b._comment b/doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_1_ae15355f54b5137e696aaf5d2111806b._comment new file mode 100644 index 0000000000..5f2da4d3a2 --- /dev/null +++ b/doc/todo/not_ask_git_credentials_for_password_per_each_file/comment_1_ae15355f54b5137e696aaf5d2111806b._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-09-09T16:02:29Z" + content=""" +Is this a git-lfs special remote, or a git remote with an annex/objects +directory? Probably does not matter, but also is unclear. + +`git credential` is doing the prompting here, and it supports caching, if +you choose to enable that, by eg `git config credential.helper cache`. + +It feels redundant to add another layer of caching to git's existing cache. +On the other hand, I suppose that `git pull` can make multiple http accesses +and reuse the same credential for them, so that's kind of a precedent for +caching during the lifetime of the process. +"""]]