Re: [PATCH 3.16 000/294] 3.16.50-rc1 review

[Arnd Bergmann]

On Thu, Nov 9, 2017 at 1:08 PM, Greg KH <greg@xxxxxxxxx> wrote:
> On Thu, Nov 09, 2017 at 12:55:30PM +0100, Arnd Bergmann wrote:
>> On Tue, Nov 7, 2017 at 12:02 AM, Ben Hutchings <ben@xxxxxxxxxxxxxxx> wrote:
>> > This is the start of the stable review cycle for the 3.16.50 release.
>> > There are 294 patches in this series, which will be posted as responses
>> > to this one.  If anyone has any issues with these being applied, please
>> > let me know.
>> >
>> > Responses should be made by Fri Nov 08 18:00:00 UTC 2017.
>> > Anything received after that time might be too late.
>> >
>> > A combined patch relative to 3.16.49 will be posted as an additional
>> > response to this.  A shortlog and diffstat can be found below.
>>
>> I haven'tr tried building the proposed patches so far, as I was waiting for
>> the kernelci builds.
>>
>> However, I see that the stable-rc/linux-3.16.y doesn't have the current
>> set, it still points to the old 3.16.35 release from last year.
>
> That's because I don't always update the stable-rc tree for other
> people's releases.  I can start doing that, just never have in the past.

I hadn't realized that you are the only one pushing to that git tree, I
simply assumed that all owners of stable kernels had write access to
all the branches.

>> I think if you upload the branch to the stable-rc git, that should produce
>> the automated build and boot results via email or via the
>> https://kernelci.org/job/ interface. Once there are some results
>> there, I'll go through the list once more to see what warnings
>> and failures remain.
>
> I don't know of a way to have others push to that tree/branch at the
> moment :(
>
> I'll go update that branch now...

Thanks!

With the arm-soc tree, we simply have a shared group-id on
gitolite.kernel.org and everyone in that group can push to it.

If that is the only thing you need, it should be trivial to let Ben
and Sasha push to /pub/scm/linux/kernel/git/stable/*.git as well,
I'm sure helpdesk@xxxxxxxxxx can arrange that. Of course if you are
worried about having multiple accounts with write access to all the
branches, then that wouldn't be enough.

     Arnd