My apologies if this has been addressed already on the list, I don't get to keep up as much as I'd like.
I've got several clients that manage config files via fossil (they're moving from git). The repos live on a network share (either NFS or CIFS). The problem is that when the fossil is opened from a second machine (one that did not initially create the repo), accessing the networked volume, it throws the following error: 'repository does not exist or is in an unreadable directory:'. We know that we can get around this error with 'rm _FOSSIL_; fossil open <fossilfile>' but it'd be great to not have this pop up on repos that are either copied (as in rsync, scp, cp, etc.. ) or accessed from multiple machines via a network share. Thanks _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
