diff options
| author | Vasant Hegde <hegdevasant@linux.vnet.ibm.com> | 2019-03-05 11:36:36 +0530 |
|---|---|---|
| committer | Stewart Smith <stewart@linux.ibm.com> | 2019-03-18 11:17:05 +1100 |
| commit | 2ba5ce84a197ee61423355f443a3ff3eea185ff1 (patch) | |
| tree | c54e22a80672fc6556100e97a19dd5e540be0990 /doc/process/stable-skiboot-rules.rst | |
| parent | c470806a2e5e25894aae772fc04069bbe35a21e4 (diff) | |
| download | skiboot-2ba5ce84a197ee61423355f443a3ff3eea185ff1.zip skiboot-2ba5ce84a197ee61423355f443a3ff3eea185ff1.tar.gz skiboot-2ba5ce84a197ee61423355f443a3ff3eea185ff1.tar.bz2 | |
Update skiboot stable tree rules
We have new mailing list (skiboot-stable@lists.ozlabs.org) for handling
stable trees!
Now onwards to submit patches to stable tree, one should send patches to
skiboot-stable@lists.ozlabs.org mailing list with subject prefix
[PATH <stable-version>] -OR- CC skiboot-stable@lists.ozlabs.org mailing
list while sending patches to upstream mailing list (skiboot@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@linux.vnet.ibm.com>
Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Diffstat (limited to 'doc/process/stable-skiboot-rules.rst')
| -rw-r--r-- | doc/process/stable-skiboot-rules.rst | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/doc/process/stable-skiboot-rules.rst b/doc/process/stable-skiboot-rules.rst index c0d4362..570bb70 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@lists.ozlabs.org list with + "[PATCH <stable version>]" in subject * This targets the patch *ONLY* to the stable branch. @@ -50,18 +51,19 @@ Two ways: commit <sha1> upstream. * If the patch has been modified, explain why in description. -2. Add "Cc: stable" above your Signed-off-by line when sending to skiboot@ +2. Add "Cc: skiboot-stable@lists.ozlabs.org" above your Signed-off-by line + when sending to skiboot@ * This targets the patch to master and stable. * You can target a patch to a specific stable tree with: :: - Cc: stable # 5.1.x + Cc: skiboot-stable@lists.ozlabs.org # 5.1.x and that will target it to the 5.1.x branch. * You can ask for prerequisites to be cherry-picked: :: - Cc: stable # 5.1.x 55ae15b Ensure we run pollers in cpu_wait_job() - Cc: stable # 5.1.x + Cc: skiboot-stable@lists.ozlabs.org # 5.1.x 55ae15b Ensure we run pollers in cpu_wait_job() + Cc: skiboot-stable@lists.ozlabs.org # 5.1.x Which means: |