linux/poky.git/documentation/contributor-guide, branch yocto-4.0.24

contributor-guide/submit-changes.rst: suggest to remove the git signature

2025-01-09T16:41:04+00:00

By default when sending patches Git adds the git version at the bottom of the patch, which is not necessary in most cases. Suggest to remove it when configuring Git when sending patches. Suggested-By: Jaekyu Lee (From yocto-docs rev: b3223f919e0445c0059cddf0ce02cb27f83582c3) Signed-off-by: Antonin Godard (cherry picked from commit d3465691231f10466703198a831a681803ffdfad) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman

contributor-guide: Remove duplicated words

2024-11-15T14:05:32+00:00

Remove "and then" as it is duplicated. (From yocto-docs rev: 09ca306a8d5fc5306388f2093541ba4110f603ea) Signed-off-by: Talel BELHAJSALEM Reviewed-by: Quentin Schulz Signed-off-by: Antonin Godard (cherry picked from commit 52ed947120e400620277a58f895294b558a9324e) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman

conf.py: rename :cve: role to :cve_nist:

2024-11-11T14:19:19+00:00

Newer versions of Sphinx already define a :cve: role that points to cve.org, instead of the role we defined in conf.py that points to nvd.nist.gov. Rename our role to :cve_nist: to avoid warnings (treated as errors). This is also backwards compatible, meaning we can build the doc with an older Sphinx if needed. The file were automatically replaced with following command: find . -name '*.rst' -exec sed -i 's/:cve:/:cve_nist:/g' {} \+ Cherry pick: * Changes on following files removed from cherry pick (not part of kirkstone): documentation/migration-guides/release-notes-4.1.1.rst documentation/migration-guides/release-notes-4.1.2.rst documentation/migration-guides/release-notes-4.1.3.rst documentation/migration-guides/release-notes-4.1.4.rst documentation/migration-guides/release-notes-4.1.rst documentation/migration-guides/release-notes-4.2.1.rst documentation/migration-guides/release-notes-4.2.2.rst documentation/migration-guides/release-notes-4.2.3.rst documentation/migration-guides/release-notes-4.2.4.rst documentation/migration-guides/release-notes-4.2.rst documentation/migration-guides/release-notes-4.3.1.rst documentation/migration-guides/release-notes-4.3.2.rst documentation/migration-guides/release-notes-4.3.3.rst documentation/migration-guides/release-notes-4.3.4.rst documentation/migration-guides/release-notes-4.3.rst documentation/migration-guides/release-notes-5.0.2.rst documentation/migration-guides/release-notes-5.0.3.rst documentation/migration-guides/release-notes-5.0.rst documentation/migration-guides/release-notes-5.1.rst * Fix minor conflicts in following files: documentation/migration-guides/release-notes-3.4.2.rst: missing :term: before CVE_PRODUCT documentation/migration-guides/release-notes-4.0.2.rst: missing :term: before PACKAGECONFIG documentation/migration-guides/release-notes-4.0.7.rst: missing cve 2022-32912 on webkitgtk Suggested-By: Quentin Schulz Reviewed-by: Quentin Schulz (From yocto-docs rev: f432e78fef82c5e5bfdfff08bb18757dc3479465) Signed-off-by: Antonin Godard (cherry picked from commit 15fa3b7e85dde50d7236c1738ad607531cc654b8) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman

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