Trent W. Buck <[EMAIL PROTECTED]> writes: > % FIXME: If --no-pristine-tree is used, and then someone changes the > % working tree, will "darcs whatsnew" break, or just be very slow? >From a quick test, it seems to stay working, albeit probably quite slowly (not so slowly with just 40 patches in the repo, though).
> % FIXME: I also expected --no-pristine-tree to break --lazy, > % since --lazy works by copying the pristine tree. When I > % tested --no-pristine-tree with a darcs-2 repo, I found that it > % copied the pristine tree! Does this mean that --no-pristine-tree is > % only for deprecated darcs-1 formats (hashed and > % old-fashioned-inventory)? I can confirm that --no-pristine-tree is ignored for hashed repos. Whether that's intentional or a bug, I can't tell. I'd consider it a documentation bug at least (or commandline parsing, if you will, I'd expect darcs to at least issue a warning that it is ignoring the flag). 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
