diff --git a/doc/bugs/resolvemerge_fails_when_unlocked_empty_files_exist/comment_2_28e204f5db91eaa258428d89cbb9f6c9._comment b/doc/bugs/resolvemerge_fails_when_unlocked_empty_files_exist/comment_2_28e204f5db91eaa258428d89cbb9f6c9._comment
new file mode 100644
index 0000000000..851ad4c39d
--- /dev/null
+++ b/doc/bugs/resolvemerge_fails_when_unlocked_empty_files_exist/comment_2_28e204f5db91eaa258428d89cbb9f6c9._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2023-05-01T21:08:48Z"
+ content="""
+I think what needs to be done here is write a simple smudge
+filter script that mocks `git-annex smuge --clean`, and see if the problem can be
+reproduced with that. That should pin down what about the behavior of that
+might be triggering what problem in git.
+"""]]