comment

2 files changed, 20 insertions, 0 deletions

diff --git a/CHANGELOG b/CHANGELOG
index 1d5472343..b2c8f6229 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -15,6 +15,9 @@ git-annex (6.20170521) UNRELEASED; urgency=medium
     an url to check if it exists. Some web servers take quite a long time
     to answer a HEAD request.
   * Windows: Win32 package has subsumed Win32-extras; update dependency.
+  * Added annex-check-command configuration, which can be used to
+    provide a shell command to check if a remote should be allowed to be
+    used at all.
 
  -- Joey Hess <id@joeyh.name>  Sat, 17 Jun 2017 13:02:24 -0400
 
diff --git a/doc/forum/Is_there_an___39__annex-cost__39___to_NEVER_access_remote__63__/comment_3_1c8f023b8d7a50cfce6d3464b12e446b._comment b/doc/forum/Is_there_an___39__annex-cost__39___to_NEVER_access_remote__63__/comment_3_1c8f023b8d7a50cfce6d3464b12e446b._comment
new file mode 100644
index 000000000..0278e8637
--- /dev/null
+++ b/doc/forum/Is_there_an___39__annex-cost__39___to_NEVER_access_remote__63__/comment_3_1c8f023b8d7a50cfce6d3464b12e446b._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2017-08-17T16:06:44Z"
+ content="""
+Another good reason to have a separate config is it should probably
+block `git annex sync` from pulling/pushing the remote. Cost does not
+affect pulling and pushing.
+
+The two config settings `annex-ignore` and
+`annex-sync` are the non-dynamic ways to control this. 
+So perhaps the way that annex-cost-command is the dynamic form of
+annex-cost, there ought to be annex-ignore-command and annex-sync-command.
+
+That also allows for situations like a network where you want git-annex
+sync to only push the git repository but not annexed contents.
+"""]]