Matt, There's "symlinks" branch that does what you want http://www.fossil-scm.org/index.html/timeline?r=symlinks
Though I haven't merged the latest Fossil changes into it yet. Related discussion: http://www.mail-archive.com/[email protected]/msg03402.html -- Dmitry Chestnykh On Mar 11, 2011, at 5:30 AM, Matt Welland wrote: > What is the plan for handling symlinks for fossil? My preference would > be for fossil to treat links as a file. Storing the pointer would be > great. Just ignoring links would also be fine by me. But actually > traversing the links is not a good idea IMHO and is a real fossil > killer. It is also not easy to work around. > > Links are commonly used to point to large amounts of static data > outside of a build area or to reference one piece of data in multiple > places. In neither of these cases would I want my scm tool to traverse > the links and add the data. A setting "ignore-links" would be an ok > compromise. > > Just my $0.02, thanks! _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
