From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [kirkstone][PATCH 0/8] documentation backports
Date: Thu, 14 Mar 2024 10:13:50 +0100 [thread overview]
Message-ID: <20240314091358.84025-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Apply relevant patches from the "master" branch.
Geoff Parker (1):
ref-manual: variables: adding multiple groups in GROUPADD_PARAM
Johan Bezem (1):
ref-manual: variables: correct sdk installation default path
Luca Ceresoli (2):
ref-manual: tasks: do_cleanall: recommend using '-f' instead
ref-manual: tasks: do_cleansstate: recommend using '-f' instead for a
shared sstate
Michael Opdenacker (3):
dev-manual: packages: fix capitalization
manuals: replace hyphens with em dashes
manuals: document VIRTUAL-RUNTIME variables
Simone Weiß (1):
contributor-guide: add notes for tests
documentation/bsp-guide/bsp.rst | 6 +-
.../contributor-guide/submit-changes.rst | 32 ++++++
documentation/dev-manual/device-manager.rst | 8 +-
documentation/dev-manual/packages.rst | 2 +-
documentation/kernel-dev/advanced.rst | 2 +-
documentation/kernel-dev/concepts-appx.rst | 2 +-
.../migration-guides/migration-1.6.rst | 26 ++---
.../migration-guides/migration-3.0.rst | 4 +-
.../migration-guides/migration-3.1.rst | 2 +-
.../migration-guides/migration-3.2.rst | 18 ++--
.../migration-guides/migration-3.3.rst | 1 -
.../migration-guides/migration-3.4.rst | 4 +-
.../migration-guides/release-notes-3.4.rst | 2 +-
documentation/overview-manual/concepts.rst | 8 +-
.../development-environment.rst | 2 +-
documentation/overview-manual/yp-intro.rst | 2 +-
documentation/profile-manual/usage.rst | 24 ++---
.../ref-manual/devtool-reference.rst | 2 +-
documentation/ref-manual/faq.rst | 4 +-
documentation/ref-manual/structure.rst | 10 +-
documentation/ref-manual/tasks.rst | 40 +++++++-
documentation/ref-manual/terms.rst | 4 +-
documentation/ref-manual/variables.rst | 99 +++++++++++++------
documentation/ref-manual/varlocality.rst | 2 +-
documentation/sdk-manual/working-projects.rst | 6 +-
documentation/test-manual/intro.rst | 4 +-
.../transitioning-to-a-custom-environment.rst | 2 +-
27 files changed, 210 insertions(+), 108 deletions(-)
--
2.34.1
next reply other threads:[~2024-03-14 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 9:13 michael.opdenacker [this message]
2024-03-14 9:13 ` [kirkstone][PATCH 1/8] ref-manual: tasks: do_cleanall: recommend using '-f' instead michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 2/8] ref-manual: tasks: do_cleansstate: recommend using '-f' instead for a shared sstate michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 3/8] ref-manual: variables: correct sdk installation default path michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 4/8] ref-manual: variables: adding multiple groups in GROUPADD_PARAM michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 5/8] dev-manual: packages: fix capitalization michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 6/8] manuals: replace hyphens with em dashes michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 7/8] contributor-guide: add notes for tests michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 8/8] manuals: document VIRTUAL-RUNTIME variables 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=20240314091358.84025-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