Blogmark

I learned about git’s range-diff from this article which is useful if you adopt this interdiff approach of evolving patch series. Rather than doing additive commits in response to reviews and CI feedback.

This is the essence of "interdiff code review." You

• Don't publish new changes on top, you publish new versions
• You don't diff between the base branch and the tip of the developer's branch, you diff between versions of commits
• Now, reviewers get an incremental review process, while authors don't have to clutter the history with 30 "address review" noise commits.
• Your basic diagnostic tools work better, with a better signal-to-noise ratio.