diff --git a/doc/todo/additional_git-annex-config_settings__63__/comment_5_ba2cbf8dcf14a1d0b20621b48b8e8600._comment b/doc/todo/additional_git-annex-config_settings__63__/comment_5_ba2cbf8dcf14a1d0b20621b48b8e8600._comment
new file mode 100644
index 0000000000..4bfab326ab
--- /dev/null
+++ b/doc/todo/additional_git-annex-config_settings__63__/comment_5_ba2cbf8dcf14a1d0b20621b48b8e8600._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="Ilya_Shlyakhter"
+ avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
+ subject="comment 5"
+ date="2021-07-12T15:30:25Z"
+ content="""
+>I do not want to add global config settings for every single git config setting
+
+Of course.  Just the settings that reflect the nature of the repo data and the intended usage processes.
+E.g. I want to be able to enforce that a repo be locked-files-only.  Or to set `maxextensionlength` based on the
+fact that the repo stores `.fastq.gz` files.
+
+>annex.supportunlocked is documented to be about avoiding extra work needed to support unlocked files, and not about preventing them from being added to a branch
+
+To me it seems more natural to have it prevent the addition of unlocked files, and be a global setting.
+"""]]