In John's case the relative path lies on the same disk and inside the working area and it would work fine on both Windows and Linux. This is also true in every one of the examples I gave.
I think the simplest solution is that on "fossil open" the path used is stored in the _FOSSIL file. Document in the help that unless you know what you are doing always use the full path and voilà, done. I suppose as an extra layer of "keep the newbie questions to a minimum" you could require a -f (i.e. force) to use relative paths. I know that developer time is a premium and this could well end up on the wish list as a low priority but I don't see any compelling technical reasons why relative paths wouldn't work fine. On Sat, Jan 28, 2012 at 2:00 PM, Stephan Beal <sgb...@googlemail.com> wrote: > On Sat, Jan 28, 2012 at 9:58 PM, Matt Welland <estifo...@gmail.com> wrote: > >> John's desired work strategy can easily be supported with the relative >> path suggestion. > > > Relative paths don't work cross-drive on Windows. They can only work on > the same drive. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
