summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorRoland Hieber <rhi@pengutronix.de>2023-09-22 12:00:05 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2023-09-25 14:37:26 +0100
commitf60c81287e916755496081d017d02aa14cb0d24c (patch)
tree42410ba6777ab952aac0435ccef483ac30752c4c /documentation
parent3dc1dbc22fe7d2468675628d414f689673c72edf (diff)
downloadpoky-f60c81287e916755496081d017d02aa14cb0d24c.tar.gz
contributor-guide: deprecate "Accepted" patch status
This is in accordance with the gatesgarth Release Notes: > In the ``Upstream-Status`` header convention for patches, > ``Accepted`` has | been replaced with ``Backport`` as these almost > always mean the same thing i.e. the patch is already upstream and > may need to be removed in a future recipe upgrade. If you are adding > these headers to your own patches then use Backport to indicate that > the patch has been sent upstream. <https://docs.yoctoproject.org/migration-guides/migration-3.2.html#miscellaneous-changes> Suggested-by: Michael Opdenacker <michael.opdenacker@bootlin.com> (From yocto-docs rev: 61813da94595a6e57c5fb5015229d601a558f299) Signed-off-by: Roland Hieber <rhi@pengutronix.de> Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/contributor-guide/recipe-style-guide.rst13
1 files changed, 5 insertions, 8 deletions
diff --git a/documentation/contributor-guide/recipe-style-guide.rst b/documentation/contributor-guide/recipe-style-guide.rst
index 7e336a0424..e03b8ff2ba 100644
--- a/documentation/contributor-guide/recipe-style-guide.rst
+++ b/documentation/contributor-guide/recipe-style-guide.rst
@@ -292,13 +292,10 @@ following status strings:
292 Submitted to upstream, waiting for approval. Optionally include where 292 Submitted to upstream, waiting for approval. Optionally include where
293 it was submitted, such as the author, mailing list, etc. 293 it was submitted, such as the author, mailing list, etc.
294 294
295``Accepted`` 295``Backport [version]``
296 Accepted in upstream, expect it to be removed at next update, include 296 Accepted upstream and included in the next release, or backported from newer
297 expected version info. 297 upstream version, because we are at a fixed version.
298 298 Include upstream version info (e.g. commit ID or next expected version).
299``Backport``
300 Backported from new upstream version, because we are at a fixed version,
301 include upstream version info.
302 299
303``Denied`` 300``Denied``
304 Not accepted by upstream, include reason in patch. 301 Not accepted by upstream, include reason in patch.
@@ -350,7 +347,7 @@ Here's an example of a patch that has been submitted upstream::
350 347
351 Signed-off-by: Joe Developer <joe.developer@example.com> 348 Signed-off-by: Joe Developer <joe.developer@example.com>
352 349
353A future update can change the value to ``Accepted`` or ``Denied`` as 350A future update can change the value to ``Backport`` or ``Denied`` as
354appropriate. 351appropriate.
355 352
356Another example of a patch that is specific to OpenEmbedded:: 353Another example of a patch that is specific to OpenEmbedded::