Hi list, 

It's about this warning when using versionable settings when it override
non-versionable setting. I understand the utility of it when overriding
a local non-versionable setting. But it also give the same warning when
overriding a global setting. Is it really necessary ?  There's no such
warning when a local setting (non-versionable) override the global
setting, so why we have when a versionable setting does ?

I know there's the .no-warn thing, but I just found this warning a bit
excessive. For my self, I would not put warning at all, but just specify
on the "fossil set" output (versionable) beside the setting like the way
it show (global) when the setting is global.

It's like, since I have a global setting for ignore-glob, I have to
create this ignore-glob.no-warn in all my repo where I use versionnable
setting. And anyway, it's not reasonnable to ask me to unset my global
setting, which have good chance to be used by other repository which
doesn't have specific needs.

Am I the only one who think like that ?

Regards

-- 
Martin G.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to