diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-08-30 16:26:44 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-09-02 07:46:30 +0100 |
commit | fb19d647697d56e7554722abb5f4903c774d4213 (patch) | |
tree | 630d8818a9124e8cac2a506344ecabf796d333e3 /README | |
parent | 703792c48c818025163de9c2f35f6ac815500607 (diff) | |
download | bitbake-fb19d647697d56e7554722abb5f4903c774d4213.tar.gz |
README: Update to point to new contributor guide
Now we have a contributor guide combining various wiki pages, point at
that.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'README')
-rw-r--r-- | README | 12 |
1 files changed, 5 insertions, 7 deletions
@@ -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 |