By peer-to-peer autosync, I mean that an instance of Fossil would automatically try to contact more than one other instance until one hosting a copy of the requested repository was found.
I work for a relatively small company that has no dedicated IT staff, so the owner does not want to run anything other than email and file serving on our server PCs. This means that we have to push and pull our changes between our work stations, which are laptops, so not always online to sync with. This is fine within the development team, our project management team will hate it. FYI, it is our intention to use Fossil only for issue tracking and documents shared with the project mangement people. Our code and development-only documents will continue to be maintained in Git. That way, there will not be copies of code or design documents on the laptops of non-developpers. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
