> if it is, it sets the local config to whatever the global was. Can you check if this is true? I'm using latest version of fossil, which doesn't exhibit this.
- Altu -----Original Message----- From: James Turner <[email protected]> To: [email protected] Sent: Thu, Nov 4, 2010 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 to whatever the global was. When a db_get is ran it checks the local config and only if it doesn't find a match does it check the global. Since I changed the global autosync setting after the fact, it doesn't get honored. So my question is, should the global config get checked before the local config? Or should local always win? I would think if after the fact I decided I want to turn autosync off globally I should be able to with out having to change autosync in each individual repository. Feel free to let me know if I've missed some obvious behavior. Thanks. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
