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: Mon, 18 Dec 2023 10:58:41 +0100 [thread overview]
Message-ID: <669b2107-8e44-4fdc-b500-f725d98bfd50@bootlin.com> (raw)
Hi Richard,
The following changes since commit 7107e18bfa4cf24b912df6c60d8ffb8c74152bca:
migration-guides: release 3.5 is actually 4.0 (2023-11-30 15:45:49 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/yocto-docs master-next
for you to fetch changes up to e52128cd0e555f16c86812a21e92f27ca5d76152:
migration-guides: add release notes for 4.0.15 (2023-12-18 10:49:00
+0100)
----------------------------------------------------------------
Etienne Cordonnier (1):
manuals: document minidebuginfo
Lee Chee Yang (2):
migration-guides: reword fix in release-notes-4.3.1
migration-guides: add release notes for 4.0.15
Michael Opdenacker (7):
test-manual: text and formatting fixes
test-manual: resource updates
test-manual: use working example
test-manual: add links to python unittest
test-manual: explicit or fix file paths
test-manual: add or improve hyperlinks
dev-manual: runtime-testing: fix test module name
Peter Kjellerstedt (1):
dev-manual: Discourage the use of SRC_URI[md5sum]
Simone Weiß (1):
manuals: brief-yoctoprojectqs: align variable order with default
local.conf
documentation/brief-yoctoprojectqs/index.rst | 4 ++--
documentation/dev-manual/debugging.rst | 17
+++++++++++++-
documentation/dev-manual/new-recipe.rst | 27
++++++++++++---------
documentation/dev-manual/runtime-testing.rst | 2 +-
documentation/migration-guides/release-4.0.rst | 1 +
documentation/migration-guides/release-notes-4.0.15.rst | 189
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
documentation/migration-guides/release-notes-4.3.1.rst | 2 +-
documentation/ref-manual/features.rst | 3 +++
documentation/test-manual/intro.rst | 112
+++++++++++++++++++++++++++++++++++++++++++--------------------------------------------
documentation/test-manual/test-process.rst | 44
+++++++++++++++++-----------------
documentation/test-manual/understand-autobuilder.rst | 62
++++++++++++++++++++++++------------------------
11 files changed, 338 insertions(+), 125 deletions(-)
create mode 100644 documentation/migration-guides/release-notes-4.0.15.rst
Thank you in advance
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2023-12-18 9:58 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 9:58 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-15 13:01 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-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=669b2107-8e44-4fdc-b500-f725d98bfd50@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).