Hi again, I should probably add, that for the LVM repository, this is not a real problem, more of an artificial one, since doing `darcs optimize` will likely remove most of the files. The result of tailor:
10:28:27 | [EMAIL PROTECTED]:~/dev/rh/lvm2 -> find tailor/_darcs -type d | while read l; do echo -n "$l: "; l $l | wc -l; done tailor/_darcs: 7 tailor/_darcs/pristine.hashed: 21328 tailor/_darcs/patches: 3118 tailor/_darcs/prefs: 3 tailor/_darcs/inventories: 3116 After doing darcs get tailor upstream (which is much faster than above, as it ignores most of the hash files in there), we get: 10:28:33 | [EMAIL PROTECTED]:~/dev/rh/lvm2 -> find upstream/_darcs -type d | while read l; do echo -n "$l: "; l $l | wc -l; done upstream/_darcs: 8 upstream/_darcs/pristine.hashed: 574 upstream/_darcs/patches: 3117 upstream/_darcs/prefs: 6 upstream/_darcs/inventories: 1 So this is a problem for repositories that have number of patches or working files on the order of tens of thousands. Just to quote our fav example: ghc-hashed/_darcs/inventories: 1 ghc-hashed/_darcs/patches: 19058 ghc-hashed/_darcs/pristine.hashed: 1205 ghc-hashed/_darcs/prefs: 7 Yours, Petr. -- Peter Rockai | me()mornfall!net | prockai()redhat!com http://blog.mornfall.net | http://web.mornfall.net "In My Egotistical Opinion, most people's C programs should be indented six feet downward and covered with dirt." -- Blair P. Houghton on the subject of C program indentation _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
