https://bugs.documentfoundation.org/show_bug.cgi?id=166723
--- Comment #11 from Telesto <[email protected]> --- (In reply to Eyal Rozenberg from comment #10) > Again, it's the opposite of what this does. It's "Accept, but suggest > not-keeping". You mentioned this before in comment 8. However don't grasp why you see/ frame it as 'Accept' Quote; "This action can be achieved by accepting the change, then undoing it while tracking." This is not totally true. If someone else made a change, you accept the change. The record vanishes fro track changes. Undo the change manually by activating Track Changes -> Record and for example retyping the previous. A) you lose the author of the original change B) You didn't truely accept the change; which implied by your action reverting it back manually. From: https://vmiklos.hu/blog/sw-redline-reinstate.html ... if a proposed insertion or deletion is not wanted, then one can reject it to push back on the proposal. So far such an action left no trace in the document, which is sometimes not wanted. Calling reinstate on a change behaves like reject, but with history: it reinstates the original state, with the rejected change preserved in the document. OK: you could say: I liked the previous better, you don't fully reject it when using reinstate. You only want to push back on the change. So 'reverse'. Which would be something like 'reverse and perserve (keep latter as a record) -- You are receiving this mail because: You are the assignee for the bug.
