From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: [master] Pull request
Date: Fri, 15 Mar 2024 14:01:39 +0100 [thread overview]
Message-ID: <d1cb2b4d-5e76-48ab-ad8f-89edbbf3e81a@bootlin.com> (raw)
Hi Richard,
The following changes since commit 9c1505eabd69af548652381cf996d44f40a4fa8a:
dev-manual: bmaptool: rename (2024-03-06 16:15:49 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/yocto-docs master-next
for you to fetch changes up to fc808b2dca4321209bfa6206d9e43aa1a5a0c5b8:
profile-manual: usage.rst: further style improvements (2024-03-15
13:57:07 +0100)
----------------------------------------------------------------
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 (8):
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
documentation: Makefile: remove releases.rst in "make clean"
migration-guides: draft notes for upcoming release 5.0
manuals: add initial stylechecks with Vale
profile-manual: usage.rst: further style improvements
Ulrich Ölmann (1):
ref-manual: classes: update description of class 'image_types'
documentation/.gitignore | 2 +
documentation/.vale.ini | 7 ++
documentation/Makefile | 15 ++-
documentation/README | 14 +++
documentation/contributor-guide/submit-changes.rst | 2 +-
documentation/migration-guides/index.rst | 1 +
documentation/migration-guides/migration-5.0.rst | 105
+++++++++++++++++++
documentation/migration-guides/release-4.0.rst | 1 +
documentation/migration-guides/release-5.0.rst | 9 ++
documentation/migration-guides/release-notes-4.0.17.rst | 238
+++++++++++++++++++++++++++++++++++++++++++
documentation/migration-guides/release-notes-5.0.rst | 66
++++++++++++
documentation/profile-manual/usage.rst | 734
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------------
documentation/ref-manual/classes.rst | 10 +-
documentation/ref-manual/variables.rst | 2 +-
documentation/standards.md | 15 +++
documentation/styles/config/vocabularies/OpenSource/accept.txt | 20 ++++
documentation/styles/config/vocabularies/Yocto/accept.txt | 5 +
17 files changed, 872 insertions(+), 374 deletions(-)
create mode 100644 documentation/.vale.ini
create mode 100644 documentation/migration-guides/migration-5.0.rst
create mode 100644 documentation/migration-guides/release-5.0.rst
create mode 100644 documentation/migration-guides/release-notes-4.0.17.rst
create mode 100644 documentation/migration-guides/release-notes-5.0.rst
create mode 100644
documentation/styles/config/vocabularies/OpenSource/accept.txt
create mode 100644
documentation/styles/config/vocabularies/Yocto/accept.txt
Thank you in advance
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2024-03-15 13:01 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 13:01 Michael Opdenacker [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-24 13:23 [master] Pull request Michael Opdenacker
2024-04-22 7:43 Michael Opdenacker
2024-04-05 16:21 Michael Opdenacker
2024-03-19 13:55 Michael Opdenacker
2024-03-06 9:10 Michael Opdenacker
2024-02-23 18:47 Michael Opdenacker
2024-02-05 14:28 Michael Opdenacker
2024-01-12 10:06 Michael Opdenacker
2024-01-09 16:21 Michael Opdenacker
2023-12-18 9:58 Michael Opdenacker
2023-12-12 9:45 Michael Opdenacker
2023-12-01 10:09 Michael Opdenacker
2023-11-17 18:57 Michael Opdenacker
2023-10-30 9:19 Michael Opdenacker
2023-10-20 13:26 Michael Opdenacker
2023-10-20 13:42 ` Richard Purdie
2023-10-09 13:22 Michael Opdenacker
2023-09-22 13:19 Michael Opdenacker
2023-09-19 14:39 Michael Opdenacker
2023-09-15 16:13 Michael Opdenacker
2023-09-08 16:59 Michael Opdenacker
2023-08-18 9:30 Michael Opdenacker
2023-08-11 18:42 Michael Opdenacker
2023-08-04 17:44 Michael Opdenacker
2023-07-28 12:49 Michael Opdenacker
2023-07-21 14:58 Michael Opdenacker
2023-06-23 17:36 Michael Opdenacker
2023-06-16 16:06 Michael Opdenacker
2023-06-02 15:10 Michael Opdenacker
2023-05-26 9:25 Michael Opdenacker
2023-05-12 8:35 Michael Opdenacker
2023-05-05 18:43 Michael Opdenacker
2023-05-03 8:45 Michael Opdenacker
2023-05-03 9:06 ` Richard Purdie
2023-04-28 13:30 Michael Opdenacker
2023-04-18 17:14 Michael Opdenacker
2023-03-31 9:36 [master] pull request Michael Opdenacker
2023-03-24 14:57 [master] Pull request Michael Opdenacker
2023-03-17 16:27 Michael Opdenacker
2023-02-24 15:39 Michael Opdenacker
2023-02-17 17:56 Michael Opdenacker
2023-02-10 10:33 Michael Opdenacker
2023-01-20 16:25 Michael Opdenacker
2023-01-06 17:11 Michael Opdenacker
2022-12-16 18:05 Michael Opdenacker
2022-12-09 18:18 Michael Opdenacker
2022-11-25 17:13 Michael Opdenacker
2022-11-10 18:35 Michael Opdenacker
2022-11-04 19:01 Michael Opdenacker
2022-10-28 13:30 Michael Opdenacker
[not found] <86dbe301-cb69-466c-8428-bb9edc5dd26b@bootlin.com>
2022-04-27 15:16 ` Richard Purdie
2021-09-17 17:44 Michael Opdenacker
2021-09-03 17:20 Michael Opdenacker
2021-08-13 13:12 Michael Opdenacker
2021-08-06 17:09 Michael Opdenacker
2021-08-02 16:30 Michael Opdenacker
2021-07-30 17:18 Michael Opdenacker
2021-07-16 18:07 Michael Opdenacker
2021-06-18 16:35 Michael Opdenacker
2021-06-14 16:29 Michael Opdenacker
2021-06-04 17:08 Michael Opdenacker
2021-05-28 16:57 Michael Opdenacker
2021-05-21 17:15 Michael Opdenacker
2021-05-07 16:06 Michael Opdenacker
2021-04-30 17:58 Michael Opdenacker
2021-04-23 15:33 Michael Opdenacker
2021-04-23 15:49 ` Richard Purdie
2021-04-15 15:02 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=d1cb2b4d-5e76-48ab-ad8f-89edbbf3e81a@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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).