linux/poky.git/documentation/contributor-guide, branch kirkstone-4.0.19

manuals: refer to new yocto-patches mailing list wherever appropriate

2024-04-19T11:50:39+00:00

There's a new yocto-patches mailing list available for all layers that do not have their own mailing list. c.f. https://lists.yoctoproject.org/g/yocto/topic/105197684 Cc: Quentin Schulz (From yocto-docs rev: d7fc3e978440d9f5724cbce85de000317a3e0783) Signed-off-by: Quentin Schulz Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: be more specific about meta-* trees

2024-04-05T14:24:00+00:00

* this is often confused to apply for e.g. meta-oe as well where it doesn't apply as meta-oe has own ML mentioned in README. (From yocto-docs rev: 98102408fe5468529e040a138f09c8fbc5fe065a) Signed-off-by: Martin Jansa Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: add notes for tests

2024-03-25T14:11:26+00:00

This adds some hints that and how changes should be tested when contributing. Fixes [YOCTO #15412] (From yocto-docs rev: 649843f4d20d1d840e1c6c4ce15e89b3a8508e0f) Signed-off-by: Simone Weiß Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: fix lore URL

2024-02-09T13:46:50+00:00

Cc: Michael Opdenacker (From yocto-docs rev: af340c7d9a327af0de14d7a6f19215866a0ea835) Signed-off-by: Baruch Siach Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: use "apt" instead of "aptitude"

2024-01-24T14:04:55+00:00

As used in the rest of the manual. (From yocto-docs rev: c68954d905f01f6cc4f7c8ceb90e77cf9068e639) Signed-off-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: fix command option

2023-12-21T16:14:00+00:00

"--subject-prefix" applies to "git format-patch", not "git send-email" (From yocto-docs rev: cf3697cebc0494a624fa2766d07c3532ec6b4341) Signed-off-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: add License-Update tag

2023-12-21T16:14:00+00:00

Porting from the old wiki https://www.openembedded.org/index.php?title=Commit_Patch_Message_Guidelines&oldid=10935#Describing_license_changes (From yocto-docs rev: 0ff60e3b3da409acff9599b1d511520051db0d37) Signed-off-by: Justin Bronder Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: style-guide: discourage using Pending patch status

2023-10-07T15:39:59+00:00

Suggested-by: Michael Opdenacker Suggested-by: Alexander Kanavin (From yocto-docs rev: 49d9c8da92cdec6fe4cdc3a4432794b9d286a24f) Signed-off-by: Roland Hieber Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: deprecate "Accepted" patch status

2023-10-07T15:39:59+00:00

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. Suggested-by: Michael Opdenacker (From yocto-docs rev: 9abc0d3100a07d93249f2fb376c42aab1bd9eb3a) Signed-off-by: Roland Hieber Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman

contributor-guide: discourage marking patches as Inappropriate

2023-10-07T15:39:59+00:00

It was never really clear what all those reasons really meant, and every patch submitted upstream liftens the maintenance on the Yocto side. So remove the current list, and replace it with two reasons in which an upstream submission likely won't benefit the upstream project. Suggested-by: Alexander Kanavin (From yocto-docs rev: e0aabb7f3e7cd28a22224740eeb794a86ab34886) Signed-off-by: Roland Hieber Reviewed-by: Michael Opdenacker Signed-off-by: Steve Sakoman