On 09/05/2016 05:23 PM, Adam Jensen wrote: > B. I suspect the storage requirement will be twice (2x) the data size - > the data is stored once in the Fossil database and another copy would > exist in the file-system [as a check-out].
I wonder if it would be nifty if Fossil could export a set (or several sets) of files as a FUSE[1] file-system? How well would that enable the case were one might want to arrange their files in various ways (branches(?)) and present [subsets of] the files as various "views" without increasing the storage requirements [significantly] (no duplication of the large files)? [1]: https://github.com/libfuse/libfuse _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
