From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 1/3] contributor-guide: add missing links to mailing lists
Date: Wed, 9 Aug 2023 16:25:18 +0200 [thread overview]
Message-ID: <20230809142520.226581-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
And fix such a link too.
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/contributor-guide/submit-change.rst | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/documentation/contributor-guide/submit-change.rst b/documentation/contributor-guide/submit-change.rst
index ba56e5986d..2555767102 100644
--- a/documentation/contributor-guide/submit-change.rst
+++ b/documentation/contributor-guide/submit-change.rst
@@ -52,7 +52,7 @@ varies by component:
For changes to other layers hosted in the Yocto Project source
repositories (i.e. ``yoctoproject.org``) and tools use the
-:yocto_lists:`Yocto Project </g/yocto/>` general mailing list.
+:yocto_lists:`yocto </g/yocto/>` general mailing list.
.. note::
@@ -63,7 +63,8 @@ For additional recipes that do not fit into the core Metadata, you
should determine which layer the recipe should go into and submit the
change in the manner recommended by the documentation (e.g. the
``README`` file) supplied with the layer. If in doubt, please ask on the
-Yocto general mailing list or on the openembedded-devel mailing list.
+:yocto_lists:`yocto </g/yocto/>` general mailing list or on the
+:oe_lists:`openembedded-devel </g/openembedded-devel>` mailing list.
You can also push a change upstream and request a maintainer to pull the
change into the component's upstream repository. You do this by pushing
--
2.34.1
next reply other threads:[~2023-08-09 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 14:25 michael.opdenacker [this message]
2023-08-09 14:25 ` [PATCH 2/3] contributor-guide: add section about why we use mailing lists michael.opdenacker
2023-08-09 15:58 ` [docs] " Frédéric Martinsons
2023-08-09 17:57 ` Richard Purdie
2023-08-09 18:55 ` Frédéric Martinsons
2023-08-10 8:33 ` Michael Opdenacker
2023-08-10 7:42 ` Daniel Ammann
2023-08-10 8:17 ` Michael Opdenacker
2023-08-09 14:25 ` [PATCH 3/3] contributor-guide: add recipe style guide michael.opdenacker
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=20230809142520.226581-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@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