Dan Pascu wrote: > > I tried today to experiment a bit with a darcs-2 hashed repository > format. > I added an empty file then made 4 changes and recorded them. I was > surprised to find that the hashed pristine directory did contain 11 > files. Every recorded change to a single file added 2 more. I was under > the impression that the hashed pristine would only contain one file for > each corresponding file in the working tree plus some index file. As it > looks right now, with files added there with every change, it is asking > for trouble with large projects (remember the 32k limit for files in a > directory with ext3). That means that even projects with less files, > but > many changes, can hit that limit.
Pristine management is certainly something that seems like it can be optimized more than the current implementation, but I think it is smarter than I think you've seen in your test... Basically, from my experience (as a user; I can't comment on the code, hopefully someone else can) darcs optimize will clean out old pristine files. But darcs optimization also happens automatically now at moments of darcs' choosing (you will see one or more "Optimizing x ..." messages from time to time if you follow the progress reports), and I've particularly noticed that pristine optimizations seem most likely to occur after large records (changes to lots of files, don't ask me what that metric is), and many pulls/pushes. -- --Max Battcher-- http://worldmaker.net _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
