I'm looking at Java refactoring - reduce cognitive complexity by extracting private methods (note: the question has been edited since I wrote this. At that time, I was looking at Revision 4) and in response to my comment that it's lacking description of the code's purpose, the author replied:
I'm not asking to review the code, I'm asking to review the refactoring. That means a review of a review. A meta-review. The refactoring intends to achieve lower complexity, better readability, better testability, better maintainability.
Is this question on-topic? Can we review this new implementation with only the original code as explanation? Or does the new code really sit for review in the usual way, with the old code merely present as illustration of an earlier attempt?
Although the specific question has now been edited, it may be worth considering what the requirements are for a changeset to be reviewable, as it's surely not the last question of this type.