On Feb 27, 2018, at 2:42 PM, Svyatoslav Mishyn <svyatoslav.mis...@gmail.com> wrote: > > So, if I want at some point to replace file by a symlink, > first need to remove that file, commit changes, > and only then add a symlink, right?
I did just that for a file here just days ago using the 2.5 release version. I’ve had no trouble due to the file -> symlink change, even when doing a “fossil update” on machines that haven’t had an update since before the change, so they’re effectively getting both changes at once. If for some reason you had to have this change appear atomically on the trunk, you could remove the file, check it in on a branch, add the symlink, check that in on the branch, and then “fossil merge --integrate symlink-fix-branch” to cause both changes to appear on trunk together. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
