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: Sun, 14 Apr 2024 20:20:02 +0200 [thread overview]
Message-ID: <20240414182011.994356-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
Picking changes from the "master" branch when applicable.
Jörg Sommer (1):
kernel-dev: join mkdir commands with -p
Lee Chee Yang (1):
release-notes-4.0.17: reorder CVEs
Michael Opdenacker (5):
manuals: fix duplicate "stylecheck" target
manuals: add initial sphinx-lint support
manuals: fix trailing spaces
manuals: fix incorrect double backticks
manuals: remove tab characters
Quentin Schulz (2):
docs: conf.py: properly escape backslashes for latex_elements
manuals: refer to new yocto-patches mailing list wherever appropriate
documentation/Makefile | 5 +-
documentation/README | 14 +++
documentation/conf.py | 4 +-
.../contributor-guide/submit-changes.rst | 2 +-
documentation/dev-manual/init-manager.rst | 2 +-
documentation/dev-manual/layers.rst | 16 +--
documentation/dev-manual/start.rst | 12 +-
documentation/dev-manual/wic.rst | 56 ++++-----
documentation/kernel-dev/advanced.rst | 4 +-
documentation/kernel-dev/common.rst | 14 +--
.../migration-guides/migration-4.0.rst | 20 +--
.../migration-guides/release-notes-4.0.17.rst | 12 +-
.../migration-guides/release-notes-4.0.5.rst | 2 +-
.../migration-guides/release-notes-4.0.rst | 17 ++-
documentation/overview-manual/intro.rst | 2 +-
documentation/profile-manual/usage.rst | 116 +++++++++---------
documentation/ref-manual/classes.rst | 2 +-
documentation/ref-manual/resources.rst | 3 +
documentation/ref-manual/tasks.rst | 2 +-
documentation/ref-manual/terms.rst | 10 +-
documentation/ref-manual/variables.rst | 2 +-
documentation/sdk-manual/working-projects.rst | 10 +-
22 files changed, 170 insertions(+), 157 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-14 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 18:20 michael.opdenacker [this message]
2024-04-14 18:20 ` [kirkstone][PATCH 1/9] release-notes-4.0.17: reorder CVEs michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 2/9] docs: conf.py: properly escape backslashes for latex_elements michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 3/9] manuals: refer to new yocto-patches mailing list wherever appropriate michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 4/9] manuals: fix duplicate "stylecheck" target michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 5/9] manuals: add initial sphinx-lint support michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 6/9] manuals: fix trailing spaces michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 7/9] manuals: fix incorrect double backticks michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 8/9] kernel-dev: join mkdir commands with -p michael.opdenacker
2024-04-14 18:20 ` [kirkstone][PATCH 9/9] manuals: remove tab characters michael.opdenacker
-- strict thread matches above, loose matches on Subject: below --
2024-03-25 13:27 [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=20240414182011.994356-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).