diff mbox series

[v2] README: Update to point to new contributor guide

Message ID 20230830153041.2015294-1-richard.purdie@linuxfoundation.org
State Accepted, archived
Commit fb19d647697d56e7554722abb5f4903c774d4213
Headers show
Series [v2] README: Update to point to new contributor guide | expand

Commit Message

Richard Purdie Aug. 30, 2023, 3:30 p.m. UTC 
Now we have a contributor guide combining various wiki pages, point at
that.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 README | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)
diff mbox series

Patch

diff --git a/README b/README
index e0f12b49f3..38a461f5c9 100644
--- a/README
+++ b/README
@@ -18,13 +18,11 @@  Bitbake requires Python version 3.8 or newer.
 Contributing
 ------------
 
-Please refer to
-https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
-for guidelines on how to submit patches, just note that the latter documentation is intended
-for OpenEmbedded (and its core) not bitbake patches (bitbake-devel@lists.openembedded.org)
-but in general main guidelines apply. Once the commit(s) have been created, the way to send
-the patch is through git-send-email. For example, to send the last commit (HEAD) on current
-branch, type:
+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 bitbake-devel@lists.openembedded.org
+The git command to do that would be:
 
     git send-email -M -1 --to bitbake-devel@lists.openembedded.org