From 2723165642466e73bbd97655bb1af3200838201b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 28 Feb 2020 13:54:32 -0400 Subject: [PATCH] comment --- ...nt_11_8badfb9c3e63f198d0e115d6ef64176d._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_11_8badfb9c3e63f198d0e115d6ef64176d._comment diff --git a/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_11_8badfb9c3e63f198d0e115d6ef64176d._comment b/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_11_8badfb9c3e63f198d0e115d6ef64176d._comment new file mode 100644 index 0000000000..8ec95ca9b5 --- /dev/null +++ b/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_11_8badfb9c3e63f198d0e115d6ef64176d._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 11""" + date="2020-02-28T17:51:47Z" + content=""" +You need to use git config to set that, not git-annex config. + +git-annex config can only be used with a few carefully +chosen configuration settings that make sense to +apply to all clones of the repository. annex.security.allowed-ip-addresses +is not amoung those. This is clearly documented in the git-annex config man +page IMHO, but I'm always interested to learn about problems with +documentation. +"""]]