i've just run into that 'sh darcs-all' updating darcs-all issue again!-(
in addition to fixing that issue, perhaps darcs-all could run 'whatsnew'
before each 'pull', and log the result somewhere?
that way, if anything else goes wrong with darcs, one might at least
safely do a 'darcs revert', then use the 'whatsnew' log to recreate
unrecorded edits to the local repo (i'm sure i'm not the only one who
avoids recording such local changes).
claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
