From 06665d733ad1919e5550ca1fd464a0e6e529e805 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 1 Mar 2021 13:52:19 -0400 Subject: [PATCH] comment --- ..._22edc4e69a686511c76c7c7608da5793._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/todo/unregisterurl_KEY_URL/comment_3_22edc4e69a686511c76c7c7608da5793._comment diff --git a/doc/todo/unregisterurl_KEY_URL/comment_3_22edc4e69a686511c76c7c7608da5793._comment b/doc/todo/unregisterurl_KEY_URL/comment_3_22edc4e69a686511c76c7c7608da5793._comment new file mode 100644 index 0000000000..bc381ba005 --- /dev/null +++ b/doc/todo/unregisterurl_KEY_URL/comment_3_22edc4e69a686511c76c7c7608da5793._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2021-03-01T17:39:31Z" + content=""" +After using setpresentkey git-annex still has the url +registered and a later addurl of a new url would make git-annex also +start trying the old url. Also, if there are several urls, you might only +want to remove one, not remove it from the web special remote entirely +as setpresentkey does. + +`rmurl --key` would be fine until a batch version was wanted, and then +something would need to be done about [[todo/git-annex-get_--batch_--key]]. +Which would be good to solve generally somehow, but otoh, `git-annex +unregisterurl` neatly avoids that more general problem. Also, it makes +sense that a registerurl user would look for a dual command like +unregisterurl before looking in rmurl for a way to do it. + +So I think unregisterurl is the right thing to add. +"""]]