From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: poky@lists.yoctoproject.org
Subject: [PATCH] README: Clarify/standardise contributions process
Date: Wed, 30 Aug 2023 16:39:27 +0100 [thread overview]
Message-ID: <20230830153927.2016454-1-richard.purdie@linuxfoundation.org> (raw)
Now we have a contributor guide combining various wiki pages, point at
that and standarise our approach across layers.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
meta-poky/README.poky.md | 15 ++-------------
meta-yocto-bsp/README.hardware.md | 15 ++++++++++++---
2 files changed, 14 insertions(+), 16 deletions(-)
diff --git a/meta-poky/README.poky.md b/meta-poky/README.poky.md
index a99c75ed5cb..7dd5e6d8316 100644
--- a/meta-poky/README.poky.md
+++ b/meta-poky/README.poky.md
@@ -34,19 +34,8 @@ For information about OpenEmbedded, see the
Contribution Guidelines
-----------------------
-The project works using a mailing list patch submission process. Patches
-should be sent to the mailing list for the repository the components
-originate from (see below). Throughout the Yocto Project, the README
-files in the component in question should detail where to send patches,
-who the maintainers are and where bugs should be reported.
-
-A guide to submitting patches to OpenEmbedded is available at:
-
-<https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded>
-
-There is good documentation on how to write/format patches at:
-
-<https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines>
+Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/
+for full details on how to submit changes.
Where to Send Patches
---------------------
diff --git a/meta-yocto-bsp/README.hardware.md b/meta-yocto-bsp/README.hardware.md
index 8ea0ef14614..a8f38cb21a6 100644
--- a/meta-yocto-bsp/README.hardware.md
+++ b/meta-yocto-bsp/README.hardware.md
@@ -33,10 +33,19 @@ The following boards are supported by the meta-yocto-bsp layer:
For more information see the board's section below. The appropriate MACHINE
variable value corresponding to the board is given in brackets.
-Reference Board Maintenance
-===========================
+Reference Board Maintenance and Contributions
+=============================================
+
+Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/
+for full details on how to submit changes.
+
+As a quick guide, patches should be sent to poky@lists.yoctoproject.org
+The git command to do that would be:
+
+ git send-email -M -1 --to poky@lists.yoctoproject.org
-Send pull requests, patches, comments or questions about meta-yocto-bsps to poky@lists.yoctoproject.org
+Send pull requests, patches, comments or questions about meta-yocto-bsp to
+poky@lists.yoctoproject.org
Maintainers: Kevin Hao <kexin.hao@windriver.com>
Bruce Ashfield <bruce.ashfield@gmail.com>
--
2.39.2
next reply other threads:[~2023-08-30 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 15:39 Richard Purdie [this message]
2023-08-30 15:55 ` [poky] [PATCH] README: Clarify/standardise contributions process Bas Mevissen
2023-08-30 16:00 ` Richard Purdie
2023-08-30 16:22 ` Bas Mevissen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230830153927.2016454-1-richard.purdie@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).