diff --git a/doc/forum/git_status_typechange_in_v5_direct_false/comment_2_19df04820aa80549cfabac0141c372c0._comment b/doc/forum/git_status_typechange_in_v5_direct_false/comment_2_19df04820aa80549cfabac0141c372c0._comment
new file mode 100644
index 0000000000..7b5d7d53b7
--- /dev/null
+++ b/doc/forum/git_status_typechange_in_v5_direct_false/comment_2_19df04820aa80549cfabac0141c372c0._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="jasonb885"
+ avatar="http://cdn.libravatar.org/avatar/c7330f4da122c671b935fc1d58bb02b1"
+ subject="oh"
+ date="2018-07-02T01:08:37Z"
+ content="""
+To usefully use files committed to git annex with digiKam, I have to have every single file unlocked. So in this case, what git status is telling me isn't useful. I can grep-v this out, but I wasn't expecting to see it since it seems like normal usage for git annex. It seems git doesn't see it that way and thinks something special has happened. I was hoping I was doing something wrong and if I used some other approach, git would be silent about the typechange. Thanks.
+"""]]