From 5d478ec38e74016812753f4b5ca951b79b322daf Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 7 Jan 2025 16:50:37 -0400 Subject: [PATCH] comment --- ..._9d724cfc7248319dcad3b57db24118fd._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/bugs/keeps_ext_remote_after_all_urls_unregistered/comment_3_9d724cfc7248319dcad3b57db24118fd._comment diff --git a/doc/bugs/keeps_ext_remote_after_all_urls_unregistered/comment_3_9d724cfc7248319dcad3b57db24118fd._comment b/doc/bugs/keeps_ext_remote_after_all_urls_unregistered/comment_3_9d724cfc7248319dcad3b57db24118fd._comment new file mode 100644 index 0000000000..1423c8377f --- /dev/null +++ b/doc/bugs/keeps_ext_remote_after_all_urls_unregistered/comment_3_9d724cfc7248319dcad3b57db24118fd._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2025-01-07T20:40:02Z" + content=""" +It would need some way for a special remote to indicate to git-annex that +it is in this unusual class of remotes where not having an url is the same as +content no longer being present in it. + +Implementing that would just make some more remotes have a special case, +which seems even harder to remember. I'd rather remove the special case, +but of course that will break existing workflows. + +And it is unusual. Consider a S3 remote. It can have an url recorded for a +object stored in it, but forgetting the url doesn't mean that the S3 bucket +no longer contains the file. If git-annex behaved this way for S3, it would +be broken in a way that could be expensive to the user. + +(The special case is not currently implemented for bittorrent special +remote. But it also doesn't record urls in a user-visible way actually.) +"""]]