The reasons given in the release notes for 1.2.0 are: 1. Overlapping working copies. 2. Very large numbers of working copies.
In my case, I use fsvs for more than one purpose. In this case, I do have one machine where I have an external drive to which I commit almost all of that machine's filesytems on a daily basis as a fast supplement to regular backups (and with much faster access to yesterdays files; I think of it akin to Vistas's file versioning). That machine does have nested working copies with fsvs, but by using "ignore" lists, there is no overlap in the repository. However, for performance, I have put the (single) WAA area in a specially created Reiser filesystem. The statistics here are probably interesting: Number of working copies: 27 find $WAA -type d -print | wc -l : 1892845 I guess it might be better if each of those working copies had its own WAA tree, but maybe fsvs will do that automatically now. ------------------------------------------------------ http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=2369694 To unsubscribe from this discussion, e-mail: [[email protected]].
