On Tue, Jan 8, 2013 at 4:08 PM, Stefan Bellon <[email protected]> wrote:
> In fact, this fossil behaviour puzzles me a lot because I tend to share > working copies via network share and at some point I end up having > _FOSSIL_ and .fslckout which are not in sync. Perhaps having a > configuration option to set the checkout filename would please all? > IN THEORY you could use this workaround: after opening from Windows, remove .fslckout. Your fossil binary on *nix will (i _think_) then see _FOSSIL_ and will (i think) use it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
