I’ve set .fossil-settings/allow-symlinks to 1 in one of my repositories, so in order to avoid the complaint from Fossil about a conflict, I also say “fossil unset allow-symlinks” in the checkout.
All is fine until I say “fossil conf pull all” command, whereupon the local setting comes back. I’ve gone into Admin > Settings on the central repository and unchecked the setting and set it to 0 for good measure, but a conf pull still resets the local setting to 0, causing a conflict. I then tried “fossil conf push all” and thereby blew away my user table and had to restore from backup. I now see how that happened: I effectively said fossil conf push user. I was incorrectly thinking that the following would push just the single settings change up to the server: fossil conf pull all fossil unset allow-symlinks fossil conf push all And if you were wondering why I pushed “all,” it’s because “fossil conf --help” did not tell me a more plausible value for AREA. I was expecting “settings” or similar. None of the other options besides “all” look plausible. Settings are neither email, nor project, shun, skin, ticket, user, or alias. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
