diff --git a/doc/todo/git-annex-migrate_using_git-replace.mdwn b/doc/todo/git-annex-migrate_using_git-replace.mdwn
index 8d3a857ac3..783b294541 100644
--- a/doc/todo/git-annex-migrate_using_git-replace.mdwn
+++ b/doc/todo/git-annex-migrate_using_git-replace.mdwn
@@ -3,3 +3,5 @@ Currently, git-annex-migrate leads to content (and metadata) being stored under
 More generally, git-annex-replace could be implemented this way, doing what git-replace does, but for git-annex keys rather than git hashes.  [[git-annex-pre-commit]] might need to be changed to implement replacement of keys added later.
 
 [[!tag needsthought]]
+
+> [[wontfix|done]], use distributed migration instead --[[Joey]]
diff --git a/doc/todo/git-annex-migrate_using_git-replace/comment_2_e760213fc51f6a2cfc68dec711622f25._comment b/doc/todo/git-annex-migrate_using_git-replace/comment_2_e760213fc51f6a2cfc68dec711622f25._comment
new file mode 100644
index 0000000000..9e4b0be36c
--- /dev/null
+++ b/doc/todo/git-annex-migrate_using_git-replace/comment_2_e760213fc51f6a2cfc68dec711622f25._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2024-02-10T14:22:31Z"
+ content="""
+In the meantime, distributed migration has been implemented, allowing
+to `git-annex migrate --update` to catch up with all migrations that were
+started elsewhere.
+
+This is essentially the same goal, and it is much more efficient in terms
+of storage than git-replace of a large number of refs.
+
+So, I'm going to close this.
+"""]]