On Tue, Dec 24, 2019, 3:13 PM 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. > They need to be merged separately too since the author is often > different on each patch. > Why does the authors matter. There is no reason a patchset or PR needs to be squashed into a single commit, they just should not be broken along the way. Also order in a patch set is usually defined by a number prefix for example this is how it is defined by the Linux kernel, but is inline with most projects that do mailing list patches. https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html#the-canonical-patch-format There is really nothing so unique about this project that we need to get too creative. --Brennan >
