Walter Landry wrote:
This is exactly what undo does. "arx undo foo" reverts all changes made to file foo. It stores it in a directory ,,undo.N. Running "arx redo" reapplies the changes. It allows you to have any number of pending changes to the tree.
Ok. If you squint, and know the secret ,,undo passcode, it does indeed do that. On a different note, I don't think undo/redo is the best name for that, since these days those terms usually work for just about any operation. Revert seems more appropriate, since undo presumably can't undo commits, or other arx commands.
I have heard this philosophy many times. Enforcing it in the tool gets wearisome. ArX is my slave, not my master. I really am sure that updating the NEWS file does not require me to run all of the tests again. If you really want to enforce this kind of thing, that is what a pqm is for.
I agree. But *allowing* someone to operate in this mode is a nice feature. Kevin _______________________________________________ Arx-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/arx-users
