forum/git-annex-sync and git-annex-configgit-annexhttp://git-annex.branchable.com/forum/git-annex-sync_and_git-annex-config/git-annexikiwiki2021-03-26T23:15:05Zcomment 1http://git-annex.branchable.com/forum/git-annex-sync_and_git-annex-config/comment_1_1372a7d54e7ef017cc4fa34358c122e0/joey2021-03-26T18:37:22Z2021-03-26T17:30:24Z
<p>If you're asking about how changes to git-annex config or conflicting
values being set in different places work, the most recent set value wins.</p>
conflicting git-annex-config valueshttp://git-annex.branchable.com/forum/git-annex-sync_and_git-annex-config/comment_2_dd5cd6f18b3d0d9cf6ad97181fcbf4b1/Ilya_Shlyakhter2021-03-26T19:27:02Z2021-03-26T19:27:02Z
I guess I was wondering if that could lead to some surprises, e.g. if someone changes <code>annex.largefiles</code> and this propagates to other users without them realizing. E.g. I'd want <a href="http://git-annex.branchable.com/forum/git-annex-sync_and_git-annex-config/todo/additional_git-annex-config_settings__63__"><code>annex.gitaddtoannex</code> and <code>annex.supportunlocked</code> added as <code>git-annex-config</code> settings</a> 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.
comment 3http://git-annex.branchable.com/forum/git-annex-sync_and_git-annex-config/comment_3_46b1ab0fcc3b9e5a974d1bf1c4d912e6/Lukey2021-03-26T21:47:38Z2021-03-26T21:47:38Z
<p>Also note that:</p>
<blockquote><p>These settings can be overridden on a per-repository basis using <code>git config</code>.</p></blockquote>
comment 4http://git-annex.branchable.com/forum/git-annex-sync_and_git-annex-config/comment_4_e4e1d59b43fc954189306de242c37dcc/Ilya_Shlyakhter2021-03-26T23:15:05Z2021-03-26T23:15:04Z
Maybe all <code>git-annex-config</code> settings should be “only read from the git-annex branch by git annex init, and is copied to the corresponding git config setting”, like <code>annex.securehashesonly</code> already is.