diff --git a/doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn b/doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn
index ff7773d3e6..0f01ae680b 100644
--- a/doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn
+++ b/doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote.mdwn
@@ -5,3 +5,5 @@ Once the two clients sync they will both have two remotes with the same name. Bu
 It would be nice to have some (automatic?) way to resolve this conflict.
 
 Not sure if anything sane can be done if both clients have pushed?
+
+> [[done]] see comment --[[Joey]]
diff --git a/doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote/comment_1_a9e54e4bc540cbab7cdbbfdeaa973f4a._comment b/doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote/comment_1_a9e54e4bc540cbab7cdbbfdeaa973f4a._comment
new file mode 100644
index 0000000000..57083fb239
--- /dev/null
+++ b/doc/todo/Wishlist__58___sanitychecker_fix_wrong_UUID__47__duplicate_remote/comment_1_a9e54e4bc540cbab7cdbbfdeaa973f4a._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2023-01-16T17:54:51Z"
+ content="""
+This does not make sense to me. If the remote is a git repo,
+it will be initialized by git-annex only once, so there will only be one
+UUID. The second "client" that uses that remote will see the earlier UUID.
+
+Unless there were some kind of a race in initializing the same repo
+concurrently, but that seems unlikely and if so this is lacking in any
+details about it.
+
+I'm going to close this since it does not make sense, but do followup if
+you remember what this was supposed to be about.
+"""]]