On Dec 21, 2017, at 2:58 PM, Peter Spjuth <[email protected]> wrote: > > I noticed that while a clone was going on another could not be done due to > the global config being locked:
I’ve seen such problems when I tried “open”ing *.fossil files with one Fossil instance that another was run against with “fossil server”. The solution I ended up with is to clone a copy on the same machine, so that one clone is “served” and the other is “opened.” On commit, the changes go first to the “opened” repo, and then are sync’d to the “served” repo. This entirely avoids the deadlock, at the expense of N+1 copies of each repo on the “fossil server” machine, where N is the number of local developers, as compared to N repo copies with the naive solution. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
