James Turner wrote:
(...)
My question is why is autosync and also localauth explicitly set in the
local repository upon creation? Couldn't they be treated like the other
settings and just have some default in the code base that gets used if
locally or globally they are not set?
So looking through the source code, I can see why the autosync global
doesn't work in my case. It would seem on repository creation, fossil
checks to see if the global autosync setting is set, if it is, it sets
the local config to whatever the global was. When a db_get is ran it
checks the local
8:05 am
Subject: Re: [fossil-users] Question about global settings
So looking through the source code, I can see why the autosync global
doesn't work in my case. It would seem on repository creation, fossil
checks to see if the global autosync setting is set, if it is, it sets
the local config
James Turner wrote:
Quick question, if I have autosync set to off globally but the
repository has it set to on...who wins?
If there is no locally defined setting, it takes the global one. If
there is a local setting defined, it will beats the global one.
From what I see the repository wins,
4 matches
Mail list logo
