https://bugs.documentfoundation.org/show_bug.cgi?id=166723
--- Comment #67 from Lars Jødal <l...@rn.dk> --- Great, we got it in time! (In reply to Miklos Vajna from comment #64) > Tuomas: if the feedback is that it needs more time, the libreoffice-25-8 > config can be also tweaked to just hide the new function so it'll show up > only on master to get more time. But I assume the proposed change from Heiko > addresses the immediate need. That could be a possibility, but do we need it? IMHO, "Reject but track" does in practice cover the meaning for the user: * Reject: The change is rejected (in the ususal sense of the word) and is gone. * Reject but Track: The change is rejected, but a track is left of it, so it is not just gone. Other users still have the possibility to use the track to put the original change back in operation, but the default will be that it ends up gone. As noted before, the change will end up gone (Reject'ed) _both_ as a result of Accept All and as a result of Reject All. Indeed, the action "Reject but Track" differs from the action "Reject". To the user, that should be clear - why otherwise have more than just "Reject"? Regarding the behaviour of "Reject but Track" on your own change, that is now discussed in bug 167194. The suggestion there does not involve the term, but whether the function should at all be allowed in that case - but let's keep that discussion to that report. -- You are receiving this mail because: You are the assignee for the bug.
