From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [nanbield][PATCH 0/6] documentation backports
Date: Tue, 27 Feb 2024 14:58:24 +0100 [thread overview]
Message-ID: <20240227135830.481147-1-michael.opdenacker@bootlin.com> (raw)
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From the updates in the "master" branch
Michael Opdenacker (5):
ref-manual: system-requirements: update packages to build docs
ref-manual: release-process: grammar fix
manuals: suppress excess use of "following" word
dev-manual: packages: clarify shared PR service constraint
dev-manual: packages: need enough free space
Simone Weiß (1):
dev-manual: Rephrase spdx creation
documentation/bsp-guide/bsp.rst | 9 ++---
documentation/dev-manual/building.rst | 2 +-
documentation/dev-manual/debugging.rst | 8 ++--
.../dev-manual/development-shell.rst | 2 +-
documentation/dev-manual/layers.rst | 8 ++--
documentation/dev-manual/libraries.rst | 4 +-
documentation/dev-manual/licenses.rst | 2 +-
documentation/dev-manual/new-machine.rst | 2 +-
documentation/dev-manual/new-recipe.rst | 8 ++--
documentation/dev-manual/packages.rst | 22 +++++++---
.../dev-manual/prebuilt-libraries.rst | 4 +-
.../dev-manual/python-development-shell.rst | 2 +-
documentation/dev-manual/qemu.rst | 4 +-
documentation/dev-manual/runtime-testing.rst | 4 +-
documentation/dev-manual/sbom.rst | 40 +++++++++++--------
.../dev-manual/speeding-up-build.rst | 4 +-
documentation/dev-manual/start.rst | 6 +--
documentation/kernel-dev/common.rst | 4 +-
.../migration-guides/migration-1.5.rst | 6 +--
.../migration-guides/migration-2.2.rst | 6 +--
.../migration-guides/migration-2.4.rst | 8 ----
.../migration-guides/migration-2.5.rst | 8 +---
.../migration-guides/migration-4.0.rst | 2 +-
documentation/overview-manual/concepts.rst | 18 ++++-----
documentation/overview-manual/yp-intro.rst | 2 +-
documentation/ref-manual/classes.rst | 8 ++--
.../ref-manual/devtool-reference.rst | 4 +-
documentation/ref-manual/faq.rst | 6 +--
documentation/ref-manual/features.rst | 2 +-
documentation/ref-manual/images.rst | 2 +-
documentation/ref-manual/release-process.rst | 8 ++--
documentation/ref-manual/structure.rst | 2 +-
.../ref-manual/system-requirements.rst | 10 ++---
documentation/ref-manual/terms.rst | 4 +-
documentation/ref-manual/variables.rst | 8 ++--
documentation/sdk-manual/appendix-obtain.rst | 10 ++---
documentation/sdk-manual/intro.rst | 2 +-
.../toaster-manual/setup-and-use.rst | 4 +-
38 files changed, 130 insertions(+), 125 deletions(-)
--
2.34.1
next reply other threads:[~2024-02-27 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 13:58 michael.opdenacker [this message]
2024-02-27 13:58 ` [nanbield][PATCH 1/6] dev-manual: Rephrase spdx creation michael.opdenacker
2024-02-27 13:58 ` [nanbield][PATCH 2/6] ref-manual: system-requirements: update packages to build docs michael.opdenacker
2024-02-27 13:58 ` [nanbield][PATCH 3/6] ref-manual: release-process: grammar fix michael.opdenacker
2024-02-27 13:58 ` [nanbield][PATCH 4/6] manuals: suppress excess use of "following" word michael.opdenacker
2024-02-27 13:58 ` [nanbield][PATCH 5/6] dev-manual: packages: clarify shared PR service constraint michael.opdenacker
2024-02-27 13:58 ` [nanbield][PATCH 6/6] dev-manual: packages: need enough free space 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=20240227135830.481147-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).