<[email protected]>
Cc: [email protected]
Bcc:
Subject: stable patch queues and submission
Reply-To:
Hi All,
With kernel.org being down, the [email protected] list is no longer working. This leaves me wondering if we should send patches directly to the various stable tree maintainers with [stable] in the prefix and linux-kernel CC'd, or if the stable queues are even being maintained during the outage.
Does anyone have a preference or suggestion on how to continue stable releases until the list comes back? (I'm assuming 'wait' isn't really a best all around option.)
josh
Re: stable patch queues and submission
Quoted 7 lines · Josh Boyer
<[email protected]>
Cc: [email protected]
Bcc:
Subject: stable patch queues and submission
Reply-To:Hi All,
Yeah... I blame Friday and mutt for that. Sorry for the lack of subject.
josh
stable patch queues and submission
In reply to Josh BoyerQuoted 7 lines
Hi All,
With kernel.org being down, the [email protected] list is no longer working. This leaves me wondering if we should send patches directly to the various stable tree maintainers with [stable] in the prefix and linux-kernel CC'd, or if the stable queues are even being maintained during the outage.
No, please do not, unless you need something "special", and even then, please cc: lkml and the developers so it's not lost.
Quoted 3 lines
Does anyone have a preference or suggestion on how to continue stable releases until the list comes back? (I'm assuming 'wait' isn't really a best all around option.)
Wait and continue to add the marking to your patches, my scripts are still running and pulling the patches out and they are going into the stable queue just fine. The queue just isn't public at the moment due to kernel.org being out.
greg k-h
Re: stable patch queues and submission
Quoted 10 lines · Greg KH
Quoted 7 lines
Hi All,
With kernel.org being down, the [email protected] list is no longer working. This leaves me wondering if we should send patches directly to the various stable tree maintainers with [stable] in the prefix and linux-kernel CC'd, or if the stable queues are even being maintained during the outage.
No, please do not, unless you need something "special", and even then, please cc: lkml and the developers so it's not lost.
Would "special" include patches that are backported for longterm releases?
Quoted 8 lines
Quoted 3 lines
Does anyone have a preference or suggestion on how to continue stable releases until the list comes back? (I'm assuming 'wait' isn't really a best all around option.)
Wait and continue to add the marking to your patches, my scripts are still running and pulling the patches out and they are going into the stable queue just fine. The queue just isn't public at the moment due to kernel.org being out.
That's good to hear, and works for new patches with CC in the commit log. I should have been more clear in that I was more curious about patches that are needed for longterm kernels but the upstream commits don't directly apply. They need to be backported and sent somewhere.
josh
Re: stable patch queues and submission
Quoted 9 lines · Josh Boyer
Quoted 8 lines · Greg KH
Quoted 7 lines
Hi All,
With kernel.org being down, the [email protected] list is no longer working. This leaves me wondering if we should send patches directly to the various stable tree maintainers with [stable] in the prefix and linux-kernel CC'd, or if the stable queues are even being maintained during the outage.
Quoted 5 lines
Quoted 2 lines
No, please do not, unless you need something "special", and even then, please cc: lkml and the developers so it's not lost.
Would "special" include patches that are backported for longterm releases?
Yes.
greg k-h
Re: stable patch queues and submission
In reply to Greg KHQuoted 11 lines · Greg KH
Quoted 7 lines
Hi All,
With kernel.org being down, the [email protected] list is no longer working. This leaves me wondering if we should send patches directly to the various stable tree maintainers with [stable] in the prefix and linux-kernel CC'd, or if the stable queues are even being maintained during the outage.
No, please do not, unless you need something "special", and even then, please cc: lkml and the developers so it's not lost.
Quoted 8 lines
Quoted 3 lines
Does anyone have a preference or suggestion on how to continue stable releases until the list comes back? (I'm assuming 'wait' isn't really a best all around option.)
Wait and continue to add the marking to your patches, my scripts are still running and pulling the patches out and they are going into the stable queue just fine. The queue just isn't public at the moment due to kernel.org being out.
I was thinking about an alternative if that can help. If the mails are sent to our addresses followed by "+stable", they're easy to filter out to another mailbox (eg: "[email protected]").
But there are a number of other reviewers on [email protected] who provide a lot of value with their reviews, and not having them check the patches could easily lead to some nasty patches leaking into stable.
Regards,
Willy
Re: stable patch queues and submission
Quoted 21 lines · Willy Tarreau
Quoted 11 lines · Greg KH
Quoted 7 lines
Hi All,
With kernel.org being down, the [email protected] list is no longer working. This leaves me wondering if we should send patches directly to the various stable tree maintainers with [stable] in the prefix and linux-kernel CC'd, or if the stable queues are even being maintained during the outage.
No, please do not, unless you need something "special", and even then, please cc: lkml and the developers so it's not lost.
Quoted 8 lines
Quoted 3 lines
Does anyone have a preference or suggestion on how to continue stable releases until the list comes back? (I'm assuming 'wait' isn't really a best all around option.)
Wait and continue to add the marking to your patches, my scripts are still running and pulling the patches out and they are going into the stable queue just fine. The queue just isn't public at the moment due to kernel.org being out.
Quoted 7 lines
I was thinking about an alternative if that can help. If the mails are sent to our addresses followed by "+stable", they're easy to filter out to another mailbox (eg: "[email protected]").
But there are a number of other reviewers on [email protected] who provide a lot of value with their reviews, and not having them check the patches could easily lead to some nasty patches leaking into stable.
I agree, and the review of the final patches during the -rc period will still happen.
I just don't want to see people start to drop using the "Cc: stable@..." as part of their patches going to Linus if they somehow think they should do something else. This proceedure is still working just fine, and when kernel.org comes back up, it will return to being an automated process.
thanks,
greg k-h