diff --git a/doc/bugs/cannot_commit___34__annex_add__34__ed_modified_file_which_switched_its_largefile_status_to_be_committed_to_git_now/comment_2_19de1d89dd0a266ce43e0f25cd2b74cd._comment b/doc/bugs/cannot_commit___34__annex_add__34__ed_modified_file_which_switched_its_largefile_status_to_be_committed_to_git_now/comment_2_19de1d89dd0a266ce43e0f25cd2b74cd._comment
index 8401b95d48..50c512e369 100644
--- a/doc/bugs/cannot_commit___34__annex_add__34__ed_modified_file_which_switched_its_largefile_status_to_be_committed_to_git_now/comment_2_19de1d89dd0a266ce43e0f25cd2b74cd._comment
+++ b/doc/bugs/cannot_commit___34__annex_add__34__ed_modified_file_which_switched_its_largefile_status_to_be_committed_to_git_now/comment_2_19de1d89dd0a266ce43e0f25cd2b74cd._comment
@@ -4,4 +4,9 @@
  date="2018-08-09T16:05:27Z"
  content="""
 The double output from `git-annex add file` is also some kind of minor bug.
+
+The double output seems to have the same root cause too: The file is left
+typechanged form by the first pass of the add, and so the second pass
+sees it again. When annex.largefiles lets the file be annexed, the doubled
+output does not occur.
 """]]