I don't know if 'markers' is the correct way to describe what I have in mind. Here the idea: Often patch contains multiple logical steps. When I review them, I follow them one at the time, and would be nice to mark them in such a way that I can immediately understand the workflow. I select a function/method/class and I color it, or I click on a button and it's hidden, or something else. This is also useful to know which part of the patch has been already reviewed: often the review process is not per file, but per logical blocks.
You need to log in before you can comment on or make changes to this bug.