- Appended to comment:
drh added on 2008-07-23 13:03:24:
Since fossil repository files have no naming conventions, it is not clear how fossil could avoid "cleaning" other repositories without opening and checking each file prior to cleaning it - which would be expensive. But I have added the feature that the current repository is not "cleaned". Nor does the current repository appear in the list of "extra" files. - Change priority to "Immediate"
- Change resolution to "Fixed"
- Change status to "Fixed"
- Change subsystem to "one"
- Change comment to "Sometimes one want to create a repository db <b>within</b> the directory that also will hold the checkout. Especially if you are com from other VCSs like e.g. Git or Darcs. I do the same, if I have a whole worktree for that I want to create an one-shot repository within. But if I ask Fossil to remove all unknown files via <tt>clean --all</tt>, it will remove its own database that the current checkout was taken from. For example: <pre> mkdir test1 cd test1 fossil new myrepos fossil open myrepos fossil add ... fossil commit : : fossil clean --all </pre> Oops, my repository is gone! I would expect, that -- at least -- every repository, that the current checkout was taken from, should be considered as a known file and should not be subject to 'clean'. Perhaps -- as a kind of loyality -- fossil should overlook all fossil repository db it ever encounter during its traversal?"
- Change foundin to "6ecc392f1c"
- Change private_contact to "c.hintze@gmx.net"
- Change severity to "Severe"
- Change status to "Open"
- Change title to "Fossil fails to recognize its repository db as a known file."
- Change type to "Incident"