You need a unique string to search&replace, and after moving from /verylonguniquepath to / you've lost that uniqueness. So to undo you'd have to store the state how it was before patching in some external file. Possible but extra code paths that need to be written and tested...
On Friday, February 5, 2016 at 9:08:56 AM UTC+1, Dima Pasechnik wrote: > > By the way, I do not see why the present binary patchning procedure cannot > get an undo mode. Then it can be used many times, to move things around. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
