Eric Kow <[EMAIL PROTECTED]> added the comment: On Tue, Sep 09, 2008 at 10:40:23 +0100, Claus Reinke wrote: > He says it is an old repository that he's pulling into, hence > lots of patches to pull. But the list of patches doesn't include > the renaming that is reported the wrong way round in whatsnew, > so it might be that pending was screwed up while he was using > an earlier darcs version.
Yes, that is precisely my poorly articulated guess. What I should have said when I first resolved this bug was: We know from the bugtracker history that the pending was corrupted prior to this pull. I surmised from the age of the repository he was pulling into that he had been working with an older darcs when it had happened, and the striking similarity this change had with issue494 and other similar repositories I saw in code.haskell.org led me to leap to to the conclusion that this was yet another issue494 manifestation, and hence an issue resolved. > All ghc repos are old, though, and have been handled > by some version of darcs 1 at some point or other, > including the repos involved in issue1034. And since > darcs does not preserve information about screwups > (issue1010), and users don't ask whatsnew in repos > they don't work in, there is no telling whether the issues > are old or new. Right. It would be nice if forensics in darcs was easier. ---------- status: chatting -> resolved __________________________________ Darcs bug tracker <[EMAIL PROTECTED]> <http://bugs.darcs.net/issue1065> __________________________________ _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
