I'm wandering how fossil handles multiple open repositories, and exactly what fossil open and close do? I've read the docs, about the dangers of losing the stash etc:
A checkout database is deleted by fossil close<http://www.fossil-scm.org/index.html/help/close>. > The fossil close command really isn't needed; one can accomplish the same > thing simply by deleting the checkout database. > > Note that the stash, the undo stack, and the state of the bisect command > are all contained within the checkout database. That means that the fossil > close command will delete all stash content, the undo stack, and the bisect > state. The close command is not undoable. Use it with care. > However I'm just trying to get my head around what fossil open does in addition to creating the checkout database and 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. I've a project with a main code base and various components that I want versioned in their own projects. So just trying to get my head around how fossil handles multiple open projects?
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
