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 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.
Maybe all git-annex-config settings should be “only read from the git-annex branch by git annex init, and is copied to the corresponding git config setting”, like annex.securehashesonly already is.
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.
annex.largefilesand this propagates to other users without them realizing. E.g. I'd wantannex.gitaddtoannexandannex.supportunlockedadded asgit-annex-configsettings 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.Also note that:
git-annex-configsettings should be “only read from the git-annex branch by git annex init, and is copied to the corresponding git config setting”, likeannex.securehashesonlyalready is.