diff --git a/doc/forum/Unlocked_files_confusion/comment_1_6442aa304b4d44bfc6bc038f4b55f37a._comment b/doc/forum/Unlocked_files_confusion/comment_1_6442aa304b4d44bfc6bc038f4b55f37a._comment
new file mode 100644
index 0000000000..51e5230475
--- /dev/null
+++ b/doc/forum/Unlocked_files_confusion/comment_1_6442aa304b4d44bfc6bc038f4b55f37a._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2019-07-19T17:02:59Z"
+ content="""
+Your .gitattributes setting configured git-annex to not
+treat metadata.db as a large file, so its content gets added to git.
+
+git-annex does not hard link locked files by ddefault, setting annex.thin
+can make it do so.
+
+There is not currently a way to configure whether a file
+is added locked or unlocked by filename. I have opened a todo
+about it, [[todo/annex.addunlocked_in_gitattributes]].
+"""]]
diff --git a/doc/todo/annex.addunlocked_in_gitattributes.mdwn b/doc/todo/annex.addunlocked_in_gitattributes.mdwn
new file mode 100644
index 0000000000..45e064e03e
--- /dev/null
+++ b/doc/todo/annex.addunlocked_in_gitattributes.mdwn
@@ -0,0 +1,11 @@
+Make annex.addunlocked be able to be configured in .gitattributes,
+the same way as annex.largefiles can be.
+
+This would be useful if certain filename extensions need to be unlocked to
+be used, and others are desired to be kept locked.
+
+The annex.addunlocked git config is a boolean, but this gitattributes one
+would effectively build up a file match expression. So it might then follow
+that the git config should also be a file match expression, with "true"
+being the same as "anything" and "false" the same as "nothing" for
+back-compat. --[[Joey]]