<div dir="ltr"><div dir="ltr">On Thu, 29 Aug 2019 at 14:54, Adrian Bunk <<a href="mailto:bunk@stusta.de">bunk@stusta.de</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
It is an unexpected meaning of "zero risk" when this excludes <br>
breakages with kernels other than the ones in master.<br>
<br>
One of the non-python changes to perf blew up the build for me even when <br>
trying with a kernel that is only a few months behind on the 4.19 branch,<br>
so there's some patches for me to send next month.<br></blockquote><div><br></div><div>This is part and parcel of using the master branch with various 'other' layers. Things can and do break in those other layers, and have to be fixed after the fact of the breaking changes landing in master. If this is not acceptable, then stable branches are far more conservative.</div><div><br></div><div>Alex<br></div></div></div>