I just noticed that when you want to recreate a repository with the same name, fossil complains about it (table blob already exists) and creates a -journal file (SQLite specific). After a new commit the journal file disappears. So, it does not really affect the behaviour of fossil, but I would rather not see the -journal file appear in the first place.
Wouldn't it be better to include a check so that you cannot recreate a repository with the same name in the same directory, based on the file name when creating the repository , avoiding the -journal file ? Secondly, why are repositories created with 'fossil new' that haven't been opened yet, not listed in the .fossil(_fossil) database / taken into account when running the 'fossil all' command ? Wim Paulussen (still working on a php interface for fossil repositories) _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
