On Tue, Nov 21, 2017 at 08:27:10PM +0000, Milosz Wasilewski wrote: > Hi, > > Is there a way to get notifications about patches queued up for the > -rc1 commits in linux-stable-rc.git? I currently use the push that is > associated with email to this list from Greg. But that only gives 48h > window to do the building and testing. If there is a way to get the > patches earlier, that would give more time for testing activities. Any > hints are much appreciated. There are multiple ways to get "notifications" about what patches are applied to the stable queue: - email to the stable-commits@vger mailing list. All patches that I apply to the stable tree are copied there, with the information about what tree they are applied to. - watch the stable-queue git tree at: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/ This is a set of patches to be applied using quilt to the specific stable tree that is referenced. There is a series file in each of the queue-X.X/ directory that you should use to know the ordering. This tree is never rebased, you can just "watch" it for updates and create a git tree from it if you want, or just apply the patches directly to a tarball from it (which is what my test system does, and I think what kernel.ci does.) - I push out updates to the linux-stable-rc.git tree in "intervals" when I am at a "stopping point": https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/ This can be at the end of a day, or when I want to get 0-day testing, or when I am about to do a -rc release. Note, this tree rebases all the time as it is automatically generated from my quilt tree of patches. Be aware of that if you use it. I also forget to push tags to it all the time, as a few developers constantly remind me... Then of course is the -rc email release announcements and patches themselves. The linux-stable-rc tree is updated at that point in time again with a "fresh" update that should not change until the "real" release happens, unless there are problems, and then it can be rebased (as happened for the last -rc release to resolve some build issues.) So, with all of those ways, is there anything lacking that you all need to be able to do your testing? thanks, greg k-h