From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [kirkstone][PATCH 0/9] documentation backports
Date: Mon, 25 Mar 2024 14:27:28 +0100 [thread overview]
Message-ID: <20240325132737.3018073-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Apply relevant patches from the "master" branch.
Alexander Kanavin (1):
dev-manual: improve descriptions of 'bitbake -S printdiff'
BELOUARGA Mohamed (1):
ref-manual: add documentation of the variable SPDX_NAMESPACE_PREFIX
Lee Chee Yang (1):
migration-guides: add release notes for 4.0.17
Martin Jansa (1):
contributor-guide: be more specific about meta-* trees
Michael Opdenacker (5):
manuals: add initial stylechecks with Vale
profile-manual: usage.rst: formatting fixes
manuals: use "manual page(s)"
profile-manual: usage.rst: fix reference to bug report
profile-manual: usage.rst: further style improvements
documentation/.gitignore | 2 +
documentation/.vale.ini | 7 +
documentation/Makefile | 13 +-
documentation/README | 14 +
.../contributor-guide/submit-changes.rst | 2 +-
documentation/dev-manual/building.rst | 7 +-
documentation/dev-manual/debugging.rst | 13 +-
.../migration-guides/release-4.0.rst | 1 +
.../migration-guides/release-notes-4.0.17.rst | 238 ++++++
documentation/profile-manual/usage.rst | 738 +++++++++---------
documentation/ref-manual/classes.rst | 2 +-
documentation/ref-manual/variables.rst | 7 +-
documentation/standards.md | 15 +
.../config/vocabularies/OpenSource/accept.txt | 20 +
.../config/vocabularies/Yocto/accept.txt | 5 +
15 files changed, 704 insertions(+), 380 deletions(-)
create mode 100644 documentation/.vale.ini
create mode 100644 documentation/migration-guides/release-notes-4.0.17.rst
create mode 100644 documentation/styles/config/vocabularies/OpenSource/accept.txt
create mode 100644 documentation/styles/config/vocabularies/Yocto/accept.txt
--
2.34.1
next reply other threads:[~2024-03-25 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 13:27 michael.opdenacker [this message]
2024-03-25 13:27 ` [kirkstone][PATCH 1/9] manuals: add initial stylechecks with Vale michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 2/9] profile-manual: usage.rst: formatting fixes michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 3/9] manuals: use "manual page(s)" michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 4/9] profile-manual: usage.rst: fix reference to bug report michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 5/9] migration-guides: add release notes for 4.0.17 michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 6/9] contributor-guide: be more specific about meta-* trees michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 7/9] profile-manual: usage.rst: further style improvements michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 8/9] ref-manual: add documentation of the variable SPDX_NAMESPACE_PREFIX michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 9/9] dev-manual: improve descriptions of 'bitbake -S printdiff' michael.opdenacker
-- strict thread matches above, loose matches on Subject: below --
2024-04-14 18:20 [kirkstone][PATCH 0/9] documentation backports 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=20240325132737.3018073-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