From 05ef86fcf337ae8ebdfb547a1608e5aa4ef34269 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 17 Aug 2017 12:05:30 -0400 Subject: [PATCH] comment --- ..._b95ce6b13ae45a2fca05260a7f77148f._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/forum/Is_there_an___39__annex-cost__39___to_NEVER_access_remote__63__/comment_2_b95ce6b13ae45a2fca05260a7f77148f._comment diff --git a/doc/forum/Is_there_an___39__annex-cost__39___to_NEVER_access_remote__63__/comment_2_b95ce6b13ae45a2fca05260a7f77148f._comment b/doc/forum/Is_there_an___39__annex-cost__39___to_NEVER_access_remote__63__/comment_2_b95ce6b13ae45a2fca05260a7f77148f._comment new file mode 100644 index 0000000000..d5f78140ce --- /dev/null +++ b/doc/forum/Is_there_an___39__annex-cost__39___to_NEVER_access_remote__63__/comment_2_b95ce6b13ae45a2fca05260a7f77148f._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2017-08-17T15:59:13Z" + content=""" +Cost settings only affect sort order, they don't allow completely blocking +use of a remote. + +I feel that it would be perhaps the wrong design to extend cost settings +into blocking a remote. + +There's also the `remote..annex-start-command` hook. However, +failure to run its command does not prevent git-annex from trying to access +a remote. + +I think it would be reasonable to add a hook +`remote..annex-check-command`. If set, the command would have +to succed, or git-annex would refuse to use the remote. +"""]]