From 5a72e3be18c1c6cc448e0ff04a661e3d1e46f4fe Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 2 Mar 2020 15:43:34 -0400 Subject: [PATCH] comment --- ...14_a908b0e465a08d60030c3e401022dad7._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_14_a908b0e465a08d60030c3e401022dad7._comment diff --git a/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_14_a908b0e465a08d60030c3e401022dad7._comment b/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_14_a908b0e465a08d60030c3e401022dad7._comment new file mode 100644 index 0000000000..841f0dc086 --- /dev/null +++ b/doc/bugs/S3-remote_fail_to_get_data_on_some_clones__47__machines/comment_14_a908b0e465a08d60030c3e401022dad7._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 14""" + date="2020-03-02T19:03:44Z" + content=""" +It's true that you can currently use git-annex config to set absolutely any +value, but git-annex only looks at the values that are listed in the +documentation. + +I suppose I'll change it to reject other values. + +---- + +So, you say it works, but I still don't understand the behavior you +originally reported. Have you somehow fixed it? Or just not reproduced it +with your new from scratch repository? +"""]]