On Wed, Dec 25, 2019 at 6:52 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > > If they are related / dependent on each other, then I think those > > kinds of patchsets should be encapsulated in one branch. > > The need to be applied and committed in sequence. Sometimes the final > patch is the one that fixes the coding style. This is inherently very > manual. >
The style fix should be in one patch not the separated patch. If the new code has the style problem, contributor should fix it and resend PR again. If the code base has the style issue, we should send new PR to fix the whole style issue. Of course, some committer may want to help fix the issue. It's fine, but the new change still need pass all check and reviewed by other committer before merge. Nobody has the right bypass the criticia we will define in the workflow document and merge the patch(even it just fix the style issue) directly.
