Ticket #158 (reopened defect)
restarting the darcs source backend skips failed changesets
|Reported by:||wfranzini||Owned by:||lele|
Description (last modified by lele) (diff)
Using the darcs source backend I've observed the following behavior:
- the target (aegis) back-end fails
- the state file seems (to me) to correctly register the last successfully applied change-set
however starting tailor again with the very same conditions skips the failed change-set, while I was expecting the same failure.
I think the darcs source back-end should obliterate a failed change-set before quitting.
- Status changed from closed to reopened
- Resolution invalid deleted