On Fri, Jun 10, 2011 at 3:49 PM, David Bovill <[email protected]> wrote:
> ...populating the directory - that is does it also open an sqlite db > connection? Some command seem to complain in certain situations that there > is not an open fossil project, and I need to close and open the project > again. > If that's happening, it's possibly because some directories are symlinks which point to outside your 'open' root. AFAIK, fossil won't (or won't always, depending on how symlinked paths are resolved) necessarily behave intuitively. It is intended that all files in a given checkout/repo live in the same directory hierarchy. If you are NOT using symlinks and you still get these errors while inside your repo then you seem to have found a bug. 'open' is analogous to the 'checkout' command of subversion or cvs. All that 'close' does is, to make an analogy based on subversion, is remove the .svn subdirs from the current checkout. i.e. it removes the checkout-contained version control metadata, such that the directory will no longer be considered to be a checked out copy of the repo. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
