On Oct 28, 2016, at 3:29 PM, Steven Gawroriski <[email protected]> wrote: > > On Fri, 30 Sep 2016 21:25:01 -0700 > "Joe Mistachkin" <[email protected]> wrote: > >> I've checked in a fix on the dirSymlinks branch that appears to >> completely fix the issue I personally encountered. >> >> I would appreciate wider testing of it. > > A bit late, but if I symlink a directory and then attempt to add it > then Fossil appears to want to add all of the files that are contained > in the specified directory. So to prevent this I symlink a normal file > then just overwrite the symlink with what I really want it to point to > (the directory).
Actually, I don’t see that it supports adding the symlink itself. Test case: mkdir x cd x f new ../x.fossil f open ../x.fossil mkdir foo ln -s foo bar f add bar f ci It complains, "nothing has changed; use --allow-empty to override” This is with the 1.36 release version: This is fossil version 1.36 [c24373934d] 2016-10-24 14:59:33 UTC _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
