Eric Sunshine <sunshine@xxxxxxxxxxxxxx> writes: > It may not be too much work for you to keep adding more (unrelated) > changes to a series, but doing so increases the burden on reviewers > unnecessarily, especially for a long patch series such as this one. > Generally speaking, each iteration should help the series converge to > the point at which it can finally land (be merged to "next"). Thus, > ideally, each iteration should have fewer changes than the previous > one. Yup. It is too easy to paint an ongoing series with a brush that is broader than necessary and say "this is to clean up", and fall into a never-ending run of scope expansion, as there always is yet another thing to clean up. The focus of the series has been to ensure that we catch error exit from "git" and that script conforms to the style guidelines, and does not include hash migration. Let's resist the urge to expand the scope. Thanks.
