>>> On 31.03.17 at 20:15, <sstabell...@kernel.org> wrote: > On Fri, 31 Mar 2017, Jan Beulich wrote: >> The other one remains, though: As indicated before, only security patches >> should be pushed to stable branches at about the same time as to >> master's staging; everything else should please wait until the patch >> has passed the push gate on master. Note, for example, how I've >> avoided including the backport of 4edb1a42e3 in the batch I've >> just pushed to 4.8-staging, despite this being a very simple and >> obvious change. > > Yes, you are right, this is important. I admit that it is the second > time that I fall into this easy mistake. Of course I ran some tests on > the backport, but I still should have waited for the push-gate. Given > that the vast majority of the backports are security fixes, which are > pushed straight way to several trees, it is easy to forget I shouldn't > do that for non-security fixes. I'll get better. But I wonder, as stable > trees maintainer, do you have a specific git configuration or a script > that helps you avoid this kind of mistakes? Or is it all by hand?
All by hand indeed. I merely have security and non-security patches queued in different places. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
