On Mar 9, 2017, at 2:24 PM, Richard Hipp <[email protected]> wrote: > > On 3/9/17, Eduard <[email protected]> wrote: >> >> Are there plans to expose the 'hash-policy' configuration option for >> modification in the fossil web interface? > > No. I was hoping to avoid yet another configuration option that > people have to think about when setting up a new Fossil instance. > hash-policy is suppose to be automatic for most users.
While I agree that the defaults are sensible and should rarely be changed, there are cases where a Fossil newbie would regret not finding this option until after commits have happened. Our newbie may be setting up a repo that they know needs to be accessible to Fossil 1.x clients, and they can’t force the upgrade. Other settings can be hidden away in the command line because the consequences of changing them are low. This option, though, is (*ahem*) a one-way function. (Thank you folks, I’ll be here all week. Try the veal.) If that argument makes you reconsider putting this in the UI, I think this setting would fit in quite nicely with what’s already in Admin > Configuration. As with the other sensible defaults there, its presence isn’t so much because it needs to be changed often, it’s because you want to be sure the user has had a chance to agree that the default is sensible early on. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
