diff --git a/doc/bugs/warning__58___unable_to_convert_submodule_to_form_that_/comment_7_4de04de71792801f50256214f4b5fe9f._comment b/doc/bugs/warning__58___unable_to_convert_submodule_to_form_that_/comment_7_4de04de71792801f50256214f4b5fe9f._comment
new file mode 100644
index 0000000000..eed218c7b9
--- /dev/null
+++ b/doc/bugs/warning__58___unable_to_convert_submodule_to_form_that_/comment_7_4de04de71792801f50256214f4b5fe9f._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 7"""
+ date="2021-01-22T18:33:01Z"
+ content="""
+Makes sense that `git-annex smudge` being called repeatedly would output
+the message like that. And unfortunately, yes, when a file is unlocked and
+gets modified, git ls-files --modified does need to smudge it. Thanks
+for clearing that part up.
+"""]]