From 2f740d14dae6b5c571cf26a9c1dcd486402538fd Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 16 Apr 2019 13:18:59 -0400 Subject: [PATCH] hmm --- ..._620388b7ef3ebcc1f9228533f07a1f86._comment | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/todo/support_multiple_special_remotes_with_same_uuid/comment_1_620388b7ef3ebcc1f9228533f07a1f86._comment diff --git a/doc/todo/support_multiple_special_remotes_with_same_uuid/comment_1_620388b7ef3ebcc1f9228533f07a1f86._comment b/doc/todo/support_multiple_special_remotes_with_same_uuid/comment_1_620388b7ef3ebcc1f9228533f07a1f86._comment new file mode 100644 index 0000000000..209935ec20 --- /dev/null +++ b/doc/todo/support_multiple_special_remotes_with_same_uuid/comment_1_620388b7ef3ebcc1f9228533f07a1f86._comment @@ -0,0 +1,23 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2019-04-16T17:09:39Z" + content=""" +Dug a little into implementing this. + +One problem is that things like `git annex dead` look up a name +in the remote list, and then use the uuid of the returned remote. +But if remote foo has sameas=bar-uuid, then the remote in the remote +list that it looks up will have that uuid, and so the uuid that will +be marked as dead is almost certianly not the one that the user expected. + +And the user can't pass the masked uuid of the sameas remote to `git-annex +dead`, because there will be no remote in the list with that uuid. + +And for that matter, the user is not likely to know the masked uuid, +because things like `git annex info` won't display it.. + +Another gotcha is that the user might make remote B with sameas=A-uuid, +and remote C with sameas=B-uuid. Which really needs to resolve to A-uuid, +so it needs to do multiple lookups, but then a sameas loop becomes a problem. +"""]]