mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2025-01-07 16:50:37 -04:00
parent a8b7328ccf
commit 5d478ec38e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
doc/bugs/keeps_ext_remote_after_all_urls_unregistered/comment_3_9d724cfc7248319dcad3b57db24118fd._comment Normal file
View file

@ -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.)
"""]]