Re: [fossil-users] Question about global settings

2010-11-04 Thread chi


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?
 
 Hopefully this will clear things up.

Now I understand better, thank you.

I think, you have a reasonable question. Your proposal, though, would
have its drawbacks too.

I -- for instance -- often take some repositories on a USB stick with
me. If the default was not established in creation, working with my
repository would depend on the global settings of the user I currently
using my repository with. This could be very confusing as well for that
use case.

But except for this, I do not see any further big drawback at the
moment. Perhaps wait whether there are further discussions concerning
this thread, and if nothing speaks against this, you could try to open
an improvement ticket with your proposal. Except -- of course -- if DRH
already rejected it here on the mailing list at that time ...


Ciao,
chi.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Question about global settings

2010-11-03 Thread James Turner
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
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Question about global settings

2010-11-03 Thread altufaltu
 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 ja...@calminferno.net
To: fossil-users@lists.fossil-scm.org
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
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] Question about global settings

2010-11-03 Thread chi
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, so what does setting it
 globally get you?

That you have not to set it for every new created repository explictly.
Only if it divert from your global policy.

For me for instance: autosync, localauth and editor are set globally
only. Only for a few reository, I did change one or another setting locally.

Ciao,
chi.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users