On Wednesday 14 January 2009, Dan Pascu wrote: > A similar problem I noticed with a darcs-1 repository and a darcs-1 > binary. Pushing (or pulling, I don't remember exactly) many changes to > a repo added an unrecorded change to the repo that I did not do. This > time it as a real diff, not just some file in a pending remove state. I > also had to darcs revert -a to get it to the desired state.
Just to clarify this, the change in the working copy after pull was not a random diff, but a partial diff of the last pulled patch. After pull the pristine and patches were just fine, but the working copy looked like it has the last pulled patch partially rolled back, as if it was not completely applied to the working tree. Same is true for the other example with the darcs-2 binary. There were 2 of the wav files moved by the final recorded patch that were not copied in the working tree, making it look like they were removed and probably that's why darcs said they were pending removal, not because it moved them first and then deleted 2 of them. I suspect that the last patch is not completely applied to the working tree in some circumstances, making it look like a partial rollback is present in the working copy. -- Dan _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
