From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: <docs@lists.yoctoproject.org>
Subject: [walnascar] Pull request
Date: Thu, 11 Dec 2025 11:23:41 +0100 [thread overview]
Message-ID: <DEVBB0EOB3KY.O2SXKMCXP0PZ@bootlin.com> (raw)
The following changes since commit 5ca6617dcceb5f5496ac9ee5d00ee9f7d3a2d5a2:
migration-guides: add release notes for 4.0.31 (2025-11-14 18:10:02 +0100)
are available in the Git repository at:
git@push.yoctoproject.org:yocto-docs walnascar-next
for you to fetch changes up to 1be4c164a9c43070e4243d34a61d31d238cf0407:
Add a new "Security" section (2025-12-11 10:52:23 +0100)
----------------------------------------------------------------
Antonin Godard (9):
ref-manual/variables.rst: NVD_DB_VERSION: fix default value
dev-manual/temporary-source-code.rst: fix definition of WORKDIR
overview-manual/yp-intro.rst: change removed ECOSYSTEM to ABOUT
overview-manual/yp-intro.rst: link to YP members and participants
ref-manual/svg/releases.svg: mark styhead and walnascar EOL
ref-manual/svg/releases.svg: mark whinlatter as current release
contributor-guide/submit-changes.rst: remove mention of Upstream-Status
Makefile: fix rsvg-convert --format capitalization
Add a new "Security" section
Lee Chee Yang (1):
migration-guides: add release notes for 5.0.14
documentation/Makefile | 4 +-
documentation/contributor-guide/submit-changes.rst | 8 +-
documentation/dev-manual/index.rst | 1 -
documentation/dev-manual/security-subjects.rst | 194 -------------------
documentation/dev-manual/temporary-source-code.rst | 14 +-
documentation/index.rst | 7 +-
documentation/migration-guides/release-5.0.rst | 1 +
.../migration-guides/release-notes-4.3.rst | 2 +-
.../migration-guides/release-notes-5.0.14.rst | 211 +++++++++++++++++++++
documentation/overview-manual/yp-intro.rst | 9 +-
documentation/ref-manual/svg/releases.svg | 16 +-
documentation/ref-manual/variables.rst | 4 +-
documentation/security-reference/index.rst | 14 ++
.../reporting-vulnerabilities.rst | 85 +++++++++
documentation/security-reference/security-team.rst | 110 +++++++++++
15 files changed, 452 insertions(+), 228 deletions(-)
delete mode 100644 documentation/dev-manual/security-subjects.rst
create mode 100644 documentation/migration-guides/release-notes-5.0.14.rst
create mode 100644 documentation/security-reference/index.rst
create mode 100644 documentation/security-reference/reporting-vulnerabilities.rst
create mode 100644 documentation/security-reference/security-team.rst
next reply other threads:[~2025-12-11 10:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 10:23 Antonin Godard [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-14 17:16 [walnascar] Pull request Antonin Godard
2025-10-29 8:36 Antonin Godard
2025-10-20 7:27 Antonin Godard
2025-10-13 16:36 Antonin Godard
2025-10-03 15:01 Antonin Godard
2025-09-26 8:52 Antonin Godard
2025-09-12 14:54 Antonin Godard
2025-08-08 16:43 Antonin Godard
2025-08-01 10:12 Antonin Godard
2025-07-11 8:34 Antonin Godard
2025-06-27 8:43 Antonin Godard
2025-06-20 7:43 Antonin Godard
2025-06-06 17:15 Antonin Godard
2025-05-26 7:55 Antonin Godard
2025-05-16 14:04 Antonin Godard
2025-04-11 7:10 Antonin Godard
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=DEVBB0EOB3KY.O2SXKMCXP0PZ@bootlin.com \
--to=antonin.godard@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