Added a comment
authoryarikoptic <yarikoptic@web>
Tue, 4 Apr 2023 20:15:59 +0000 (20:15 +0000)
committeradmin <admin@branchable.com>
Tue, 4 Apr 2023 20:15:59 +0000 (20:15 +0000)
doc/bugs/registerurl_does_not_register_if_external_remote/comment_2_0f4d7c7f208b965ece8f017a38d7d0f1._comment [new file with mode: 0644]

diff --git a/doc/bugs/registerurl_does_not_register_if_external_remote/comment_2_0f4d7c7f208b965ece8f017a38d7d0f1._comment b/doc/bugs/registerurl_does_not_register_if_external_remote/comment_2_0f4d7c7f208b965ece8f017a38d7d0f1._comment
new file mode 100644 (file)
index 0000000..1c6e9a2
--- /dev/null
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 2"
+ date="2023-04-04T20:15:59Z"
+ content="""
+yet to re-review that reasoning, but does it mean that to merely register a URL client needs to
+- call `annex registerurl`
+- inspect to which remote URL was added/was claimed (is there a way? `whois` is silent)
+- if it was claimed by some special remote other than web -- use `annex setpresentkey`?
+
+Sounds like too much / too fragile, and somewhat different from how `addurl` behaves which does it all just fine regardless either it is web or some claimurl'ed remote.
+"""]]