On Tue, Aug 7, 2018 at 12:29 AM Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: > > On Mon, 6 Aug 2018, Nick Desaulniers wrote: > > On Sun, Aug 5, 2018 at 1:33 PM tip-bot for Nick Desaulniers > > <tipbot@xxxxxxxxx> wrote: > > > Cc: stable@xxxxxxxxxxxxxxx > > > > Not sure if this was going to be cleaned up in an automated way, but > > looks like this commit message drops the comment to stable as to how > > far back it should go: > > > > # 4.17, 4.14, 4.9, 4.4 > > The Fixes tag is enough. If the upstream commit was backported, then the > tools of the stable folks will find it and know exactly how far it needs to > go back. Oh, cool. > > also, there were tested by's reported: > > > > Tested-by: David Laight <david.laight@xxxxxxxxx> > > Tested-by: Sedat Dilek <sedat.dilek@xxxxxxxxx> > > Which came in after I applied it.... I've seen other maintainers revise commit messages before sending pull requests along, but I guess that's problematic as anyone else who has pulled before the revision would then have a merge conflict. -- Thanks, ~Nick Desaulniers -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|