WHEN she restores a backup using gsb rewind and provides the command-line flag --delete-original
THEN upon successfully rewinding to the desired state, the backup that she restored will be deleted from the linear history, just as if she had run gsb delete <original_backup> herself
SO her history is not unnecessarily cluttered with two restore points that share the same state (and so she can hopefully free up some disk space the next time she runs a gc)
Notes
No shortname for --delete-original, as there's no good way to undo this
At the time of writing I do not the original tagname should just be updated to point to the restore point
Spun off from #42
GIVEN M.A.R.I.L.L.A is managing large game saves
WHEN she restores a backup using
gsb rewindand provides the command-line flag--delete-originalTHEN upon successfully rewinding to the desired state, the backup that she restored will be deleted from the linear history, just as if she had run
gsb delete <original_backup>herselfSO her history is not unnecessarily cluttered with two restore points that share the same state (and so she can hopefully free up some disk space the next time she runs a
gc)Notes
--delete-original, as there's no good way to undo this