diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_28_34a211315186fed74d3e8c22aa65f1a2._comment b/doc/forum/lets_discuss_git_add_behavior/comment_28_34a211315186fed74d3e8c22aa65f1a2._comment
new file mode 100644
index 0000000000..1dfc709663
--- /dev/null
+++ b/doc/forum/lets_discuss_git_add_behavior/comment_28_34a211315186fed74d3e8c22aa65f1a2._comment
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="amindfv@6f75355c5dad3450ed73d1f01715be90dfdd6cd6"
+ nickname="amindfv"
+ avatar="http://cdn.libravatar.org/avatar/9cdda587f634ea9a85b34b25be421676"
+ subject="comment 28"
+ date="2019-10-23T04:42:36Z"
+ content="""
+> Several commenters seem to be under the misapprehension that git add of a modified file that is stored in git before will annex the new version. It does not.
+
+For what it's worth, this wasn't a misapprehension that I had in my posts above. It's possible I conflated or wasn't clear enough about other concerns in a way that created that impression (or maybe you simply weren't talking about my posts!), but my concerns are about:
+
+  - Loss of control of what's added to git vs. git-annex
+  - Violating the Principle of Least Astonishment
+  - Too much \"magic\" requiring me to work against, instead of with, my tools
+  - Breaking my and others' existing git-annex workflows
+
+All of which are relevant to adding new files to the repo.
+"""]]