On Thu, May 03, 2007 at 04:54:54PM +0100, Claus Reinke wrote: > >>that is odd, the file is still here, just that darcs has forgotten about > >>it. > > > >Darcs ought to remove it if you don't have any local changes to it. > > there were no local changes in that file.
Well, sounds like a bug, but not much that can be done without knowing how to reproduce it. It could, for example, have been removed in the same batch of patches that caused darcs to trip over altering darcs-all. > >Is darcs whatsnew --look-for-adds --no-summary > > yes! that is helpful, thanks. i wasn't aware that the effect of -l is not > the default (i thought that uninteresting output was avoided via boring > only - is that what 'cvs diff' used to do?). I think cvs and darcs have the same behaviour, although I wouldn't swear to it. I guess the reason is that it's common to redirect compilation output etc to a file in the working directory, and you don't want whatsnew (or, more importantly, record) picking that up. > >Note that at the moment the Makefiles in libraries/* won't do the right > >thing. They're waiting for me to get around to looking at "Setup > >makefile". > > i usually build only from the top of the ghc tree, so will only be affected > indirectly. anything in particular i shouldn't expect to work yet? Everything from the top of the tree should be working. Thanks Ian _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
