1
0
mirror of https://git.yoctoproject.org/poky synced 2026-05-08 05:09:24 +00:00

contributor guide: remove unnecessary information about mailing lists

The mailing lists for sending code are sufficient!

(From yocto-docs rev: 2ea840c34043d4d630ad2deae0ffd285503d1078)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker
2023-08-10 17:27:42 +02:00
committed by Richard Purdie
parent f004fa65c6
commit 9e3b852770
@@ -226,9 +226,7 @@ Using Email to Submit a Patch
Depending on the components changed, you need to submit the email to a
specific mailing list. For some guidance on which mailing list to use,
see the ":ref:`contributor-guide/submit-change:finding a suitable mailing list`"
section above. For a description of all the available
mailing lists, see the ":ref:`Mailing Lists <resources-mailinglist>`" section in the
Yocto Project Reference Manual.
section above.
Here is the general procedure on how to submit a patch through email
without using the scripts once the steps in
@@ -369,10 +367,9 @@ have been followed:
you can see who is responsible for the bulk of the changes against
the file.
- *Examine the List of Mailing Lists:* For a list of the Yocto
Project and related mailing lists, see the ":ref:`Mailing
lists <resources-mailinglist>`" section in
the Yocto Project Reference Manual.
- *Find the Mailing List to Use:* See the
":ref:`contributor-guide/submit-change:finding a suitable mailing list`"
section above.
#. *Make a Pull Request:* Notify the maintainer or the mailing list that
you have pushed a change by making a pull request.