Discard Changes
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): mailman.1.1244516401.12212.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Hi!
I found the item "checkpoint rollback" in the todo-list. By "checkpoint rollback" you mean discarding all changes since a given checkpoint?
Such a feature would be *very* nice! I can't imagine that it should be very complicated to implement, but I might be wrong.
In SIMPLUX (a live distribution) users shall have a chance to abolisch all changes made in a session. So I would create a snapshot at each startup and remove all checkpoints created afterwards to revert to the previous state if user decides to do so.
Greetings, Michael
Hi,
Quoted 4 lines · Dipl.-Ing. Michael Niederle
Hi!
I found the item "checkpoint rollback" in the todo-list. By "checkpoint rollback" you mean discarding all changes since a given checkpoint?
Yes, exactly.
Quoted 9 lines
Such a feature would be *very* nice! I can't imagine that it should be very complicated to implement, but I might be wrong.
In SIMPLUX (a live distribution) users shall have a chance to abolisch all changes made in a session. So I would create a snapshot at each startup and remove all checkpoints created afterwards to revert to the previous state if user decides to do so.
Greetings, Michael
I imagine it is likely be compilcated in NILFS because a few metadata files have no past versions in the current implementation.
Nilfs can change checkpoints to snapshots in later. So, I think the rollback feature should inherit this characteristics. That is, rollback without a prior make-snapshot operation.
Cheers,
Ryusuke Konsihi