From f84bfdefe6c7c1544f63b1a411069a584756c44a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 11 Nov 2024 14:21:44 -0400 Subject: [PATCH] response --- ...nt_2_c3754e2f52aa3094c1d1345dfdb014dd._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/git-annex-reregisterurl/comment_2_c3754e2f52aa3094c1d1345dfdb014dd._comment diff --git a/doc/git-annex-reregisterurl/comment_2_c3754e2f52aa3094c1d1345dfdb014dd._comment b/doc/git-annex-reregisterurl/comment_2_c3754e2f52aa3094c1d1345dfdb014dd._comment new file mode 100644 index 0000000000..988ed4bcee --- /dev/null +++ b/doc/git-annex-reregisterurl/comment_2_c3754e2f52aa3094c1d1345dfdb014dd._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""Re: cannot "unregister" fully""" + date="2024-11-11T18:18:38Z" + content=""" +You can use `git-annex setpresentkey` to tell git-annex that content is not +present in your special remote. + +Usually whether or not an url is currently registered with a special remote +does not affect whether content is actually stored in it, which is why +these are 2 different things. Except for the web special remote, which is a +special case. I guess yours special remote also may be a special case, but +git-annex doesn't know about it, and so why not use setpresentkey to handle +the special case, rather than further complicating reregisterurl with it? +"""]]