From d727907795ddb7848389dd429385cfc0bc93c211 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 17 Apr 2023 13:48:23 -0400 Subject: [PATCH] comment --- ...1_136c0fa106347bd0474f8298fde227f5._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/Disabling_remote_auto-enabling_not_possible/comment_1_136c0fa106347bd0474f8298fde227f5._comment diff --git a/doc/bugs/Disabling_remote_auto-enabling_not_possible/comment_1_136c0fa106347bd0474f8298fde227f5._comment b/doc/bugs/Disabling_remote_auto-enabling_not_possible/comment_1_136c0fa106347bd0474f8298fde227f5._comment new file mode 100644 index 0000000000..3e9a9c8a3b --- /dev/null +++ b/doc/bugs/Disabling_remote_auto-enabling_not_possible/comment_1_136c0fa106347bd0474f8298fde227f5._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2023-04-17T17:42:31Z" + content=""" +`git-annex dead` will work. + +But it does seem to me that there is perhaps room to have a way +to clear the autoenable setting without killing the remote entirely, +but without needing to be able to enableremote the remote. + +And I think, when you say "The special remote is (no longer) accessible to +everyone" you mean some people still have access, right? But you're not +one of those people and want to disable the autoenable. + +If so, I ought to add something like `git-annex configremote foo +autoenable=false`. +"""]] -- 2.30.2