From f4a281f7127454e91226690a4fc342cecf898efe Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 13 Jul 2021 03:05:45 +0000 Subject: [PATCH] Added a comment --- .../comment_7_c1768ab8568c8e58525ed40e76cc13f2._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/additional_git-annex-config_settings__63__/comment_7_c1768ab8568c8e58525ed40e76cc13f2._comment diff --git a/doc/todo/additional_git-annex-config_settings__63__/comment_7_c1768ab8568c8e58525ed40e76cc13f2._comment b/doc/todo/additional_git-annex-config_settings__63__/comment_7_c1768ab8568c8e58525ed40e76cc13f2._comment new file mode 100644 index 0000000000..10d506ec08 --- /dev/null +++ b/doc/todo/additional_git-annex-config_settings__63__/comment_7_c1768ab8568c8e58525ed40e76cc13f2._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 7" + date="2021-07-13T03:05:45Z" + content=""" +Realized that for the use case I was thinking of -- setting repo-wide policies such as locked-files-only -- git-annex-config isn't right, since the value can be changed by any clone. For that use case, have to configure hooks/triggers on the central repo to reject pull requests that break the policy. +"""]]