Eric Kow <[email protected]> writes: > See if there are any other variants of the filename 'irates' (like > iRates) in the history. Eric, I think your assumption about filenames is wrong. I think the hunk simply is corrupt, likely resulting from a record with a corrupt pristine.
> If we do find something like this, and unless somebody else has a > cleaner solution, we'll have to do something which amounts to re-writing > history. You will likely have to rewrite history, yes. Probably in a text editor, too. The right thing to do is to get a copy of the repo up to the bad patch. Then taking a diff of the bad patch and trying to apply it by hand. That should fail, and you should be able to find out why. Then you should rewrite the diff so that it applies, and afterwards you should (in a old-fashioned copy of the repo) find the same patch in _darcs/patches, do the same edit and then make a new hashed copy. There may be some difficulty in obtaining the old-fashioned copy, since get fails. I'd think that it *may* populate _darcs/patches first -- if that's the case, you should be able to edit the patch, then darcs repair (which should pass now) and then get the "fixed" copy. Yours, Petr. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
