This requires a lot of work on fossils part in order to be reliable. Unlike
source changes, you can't do a commit and then require a merge before
pushing if there's a collision. There are also nasty restrictions on how you
do things. In particular, you have to have autosync on (or ignore it if off)
and be connected to all repositories you push/pull from to use it.
Given those restrictions, if you're looking to change things to support
fossil, wouldn't you be better off using a tool designed for managing
binaries ( an artifact repository) instead of one designed for managing
textual sources?
<mike
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
