[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YhOeqJ0XLjYVuBCe@kroah.com>
Date: Mon, 21 Feb 2022 15:16:08 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Pavel Machek <pavel@...x.de>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
slade@...dewatkins.com
Subject: Re: [PATCH 4.19 00/58] 4.19.231-rc1 review
On Mon, Feb 21, 2022 at 01:23:40PM +0100, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 4.19.231 release.
> > There are 58 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
>
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> > and the diffstat can be found below.
>
> Do you think you could quote git hash of the respective commit here?
No, as that tree is a "throw away" one which I delete instantly on my
side once I create it and push it out. I am only creating it so that
people who use git for their CI can have an easy way to test it.
Once I do a -rc announcement, the branch here should always work, if
not, please report it.
thanks,
greg k-h
Powered by blists - more mailing lists