From f49c6fa9d225cc2d0e007eec37603f8c7272602d Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 26 Mar 2021 19:27:05 +0000 Subject: [PATCH] Added a comment: conflicting git-annex-config values --- .../comment_2_dd5cd6f18b3d0d9cf6ad97181fcbf4b1._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/git-annex-sync_and_git-annex-config/comment_2_dd5cd6f18b3d0d9cf6ad97181fcbf4b1._comment diff --git a/doc/forum/git-annex-sync_and_git-annex-config/comment_2_dd5cd6f18b3d0d9cf6ad97181fcbf4b1._comment b/doc/forum/git-annex-sync_and_git-annex-config/comment_2_dd5cd6f18b3d0d9cf6ad97181fcbf4b1._comment new file mode 100644 index 0000000000..0b176677e4 --- /dev/null +++ b/doc/forum/git-annex-sync_and_git-annex-config/comment_2_dd5cd6f18b3d0d9cf6ad97181fcbf4b1._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="conflicting git-annex-config values" + date="2021-03-26T19:27:02Z" + content=""" +I guess I was wondering if that could lead to some surprises, e.g. if someone changes `annex.largefiles` and this propagates to other users without them realizing. E.g. I'd want [`annex.gitaddtoannex` and `annex.supportunlocked` added as `git-annex-config` settings](todo/additional_git-annex-config_settings__63__) so they get set when someone first clones a repo, but the prospect of someone silently changing these settings in my existing clone gives pause. +"""]]