[Skiboot] [PATCH] Update skiboot stable tree rules
stewart at linux.ibm.com
Wed Mar 6 09:21:07 AEDT 2019
Andrew Donnellan <andrew.donnellan at au1.ibm.com> writes:
> On 5/3/19 5:06 pm, Vasant Hegde wrote:
>> We have new mailing list (skiboot-stable at lists.ozlabs.org) for handling
>> stable trees!
>> Now onwards to submit patches to stable tree, one should send patches to
>> skiboot-stable at lists.ozlabs.org mailing list with subject prefix
>> [PATH <stable-version>] -OR- CC skiboot-stable at lists.ozlabs.org mailing
>> list while sending patches to upstream mailing list (skiboot at lists.ozlabs.org).
>> This will remove the requirement to do the --suppress-cc OR other related
>> --no-cc-* options from git-send-email to remove "CC" list.
>> Signed-off-by: Vasant Hegde <hegdevasant at linux.vnet.ibm.com>
>> doc/process/stable-skiboot-rules.rst | 12 +++++++-----
>> 1 file changed, 7 insertions(+), 5 deletions(-)
>> diff --git a/doc/process/stable-skiboot-rules.rst b/doc/process/stable-skiboot-rules.rst
>> index c0d4362c1..570bb70ed 100644
>> --- a/doc/process/stable-skiboot-rules.rst
>> +++ b/doc/process/stable-skiboot-rules.rst
>> @@ -32,7 +32,8 @@ What patches are accepted?
>> HOWTO submit to stable
>> Two ways:
>> -1. Send patch to the skiboot@ list with "[PATCH stable]" in subject
>> +1. Send patch to the skiboot-stable at lists.ozlabs.org list with
>> + "[PATCH <stable version>]" in subject
>> * This targets the patch *ONLY* to the stable branch.
> If we're not going to send stable-targeted patches to the main skiboot
> list, we're going to want to make sure this is announced very, very
> loudly so everyone actually subscribes to skiboot-stable...
I guess we could also say "cc to skiboot-stable@" ?
The aim is to have things be easy for Vasant to manage stable branches,
but also need to make sure things are easy for people to submit things.
OPAL Architect, IBM.
More information about the Skiboot