[Skiboot] stable trees and process

Stewart Smith stewart at linux.ibm.com
Fri May 25 14:44:58 AEST 2018

Andrew Donnellan <andrew.donnellan at au1.ibm.com> writes:
> On 25/05/18 11:39, Stewart Smith wrote:
>> Hey all,
>> So, we do major releases and have stable trees, with some specified
>> process around doing stable (see
>> https://open-power.github.io/skiboot/doc/stable-skiboot-rules.html ).
>> Although the *reality* has been a bit more ad-hoc, with candidates for
>> stable being from either me talking to people on email, slack or in
>> (often IBM-internal) bug reports.
>> I'd like to change that, and have us follow the above process.
>> That is, *use* the "CC: stable" tag when a fix needs to get to a stable
>> tree.
>> So, if a patch needs to get to a service pack for an IBM firmware
>> release, it needs to get into a stable tree. (the same is probably also
>> true for other openpower system vendors)
> Pro tip, because I've done this several times, don't add "Cc: stable" to 
> your skiboot patch, and then by the magic of git send-email with a 
> mailrc configured, accidentally have that turn into a Cc to 
> stable at vger.kernel.org...

Heh - there's some magic flags to git send-email to avoid that I
believe. I keep forgetting them though. Maybe we need an actual address
just to circumvent git being "Smart"?

Stewart Smith
OPAL Architect, IBM.

More information about the Skiboot mailing list