[email protected] (Trent W. Buck) writes: > Pathological example: I have a file with a large number of changed > files. One of these, "foo", has grown from an empty file to a one-line > file.
> If I run "darcs whatsnew foo", i.e. restricting the whatsnew check to > that single file, will it take noticably longer to read foo *and* the > huge index (with hashed-storage) as compared to just reading foo (which, > theoretically, is what Darcs 2.2 does)? The catch here is that darcs whatsnew foo with hashed-storage won't read the huge index file either, just the relevant part of it (although it currently isn't as efficient as it should be). -- 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
