From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Jon.Mason@arm.com, JPEWhacker@gmail.com,
Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH 01/10] contributor-guide: move to 2nd place in top menu
Date: Fri, 18 Aug 2023 19:09:56 +0200 [thread overview]
Message-ID: <20230818171005.92381-2-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230818171005.92381-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To give it more visibility
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/index.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/index.rst b/documentation/index.rst
index 4d0231503d..3fef1704a4 100644
--- a/documentation/index.rst
+++ b/documentation/index.rst
@@ -26,6 +26,7 @@ Welcome to the Yocto Project Documentation
:caption: Manuals
Overview and Concepts Manual <overview-manual/index>
+ Contributor Guide <contributor-guide/index>
Reference Manual <ref-manual/index>
Board Support Package (BSP) Developer's guide <bsp-guide/index>
Development Tasks Manual <dev-manual/index>
@@ -34,7 +35,6 @@ Welcome to the Yocto Project Documentation
Application Development and the Extensible SDK (eSDK) <sdk-manual/index>
Toaster Manual <toaster-manual/index>
Test Environment Manual <test-manual/index>
- Contributor Guide <contributor-guide/index>
bitbake
.. toctree::
--
2.34.1
next prev parent reply other threads:[~2023-08-18 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 17:09 [PATCH 00/10] Further work on the Contributor Manual michael.opdenacker
2023-08-18 17:09 ` michael.opdenacker [this message]
2023-08-18 17:09 ` [PATCH 02/10] contributor-guide: submit-changes: simplify note michael.opdenacker
2023-08-18 17:09 ` [PATCH 03/10] contributor-guide: identify component: provide link to repositories michael.opdenacker
2023-08-18 17:09 ` [PATCH 04/10] contributor-guide: submit-changes: detail commit and patch creation michael.opdenacker
2023-08-18 17:10 ` [PATCH 05/10] contributor-guide: submit-changes: develop sending patches section michael.opdenacker
2023-08-18 17:10 ` [PATCH 06/10] manuals: README: update list of manuals michael.opdenacker
2023-08-18 17:10 ` [PATCH 07/10] contributor-guide: submit-changes: reorganize and develop sections michael.opdenacker
2023-08-18 17:10 ` [PATCH 08/10] contributor-guide: submit-changes: improvements to mailing lists section michael.opdenacker
2023-08-18 17:10 ` [PATCH 09/10] contributor-guide: submit-changes: commit guidelines for recipes michael.opdenacker
2023-08-18 17:10 ` [PATCH 10/10] contributor-guide: submit-changes: how to request push access to repositories 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=20230818171005.92381-2-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=JPEWhacker@gmail.com \
--cc=Jon.Mason@arm.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