public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: <docs@lists.yoctoproject.org>
Subject: [whinlatter] Pull request
Date: Tue, 13 Jan 2026 10:54:04 +0100	[thread overview]
Message-ID: <DFNDCBAFKMQ0.1SZFJLNOJEVLX@bootlin.com> (raw)

The following changes since commit 102a33294e63a5581c413555040f790161fc80ff:

  Fix bitbake version mapping for whinlatter (2026-01-09 15:00:43 +0000)

are available in the Git repository at:

  git@push.yoctoproject.org:yocto-docs whinlatter-next

for you to fetch changes up to ea0501a135043aefc7c6049be811f4c1277f1f8b:

  contributor-guide/recipe-style-guide.rst: explain difference between layer and recipe license(s) (2026-01-13 09:59:23 +0100)

----------------------------------------------------------------
Antonin Godard (12):
      Add a new "Security" section
      Add a security manual
      Move security related manuals to the security manual
      security-manual/securing-images.rst: remove old links
      test-manual/ptest.rst: detail the exit code and output requirements
      ref-manual/release-process.rst: add a "Development Cycle" section
      overview-manual/yp-intro.rst: fix SDK type in bullet list
      overview-manual: convert YP-flow-diagram.png to SVG
      Remove diagrams directory
      dev-manual/qemu: add an example for the snapshot+nographic mode
      ref-manual/variables.rst: document the CCACHE_TOP_DIR variable
      contributor-guide/recipe-style-guide.rst: explain difference between layer and recipe license(s)

 diagrams/poky-buildprocess/Pokyarch_diag.jpg       |  Bin 285707 -> 0 bytes
 diagrams/poky-buildprocess/Pokyarch_diag.svg       |  205 ---
 diagrams/poky-buildprocess/Pokyarch_diag2.svg      | 1544 --------------------
 diagrams/poky-buildprocess/pokyarch4.dia           |  Bin 3495 -> 0 bytes
 diagrams/poky-buildprocess/pokyarch4.png           |  Bin 52531 -> 0 bytes
 .../contributor-guide/recipe-style-guide.rst       |   14 +
 documentation/contributor-guide/submit-changes.rst |    2 +-
 documentation/dev-manual/index.rst                 |    4 -
 documentation/dev-manual/qemu.rst                  |   11 +
 documentation/dev-manual/sbom.rst                  |    2 +-
 documentation/dev-manual/security-subjects.rst     |  194 ---
 documentation/index.rst                            |    8 +-
 .../migration-guides/release-notes-4.2.rst         |    2 +-
 .../migration-guides/release-notes-4.3.rst         |    2 +-
 documentation/overview-manual/concepts.rst         |    4 +-
 .../overview-manual/figures/YP-flow-diagram.png    |  Bin 190715 -> 0 bytes
 .../overview-manual/svg/yp-flow-diagram.svg        |  950 ++++++++++++
 documentation/overview-manual/yp-intro.rst         |    5 +-
 documentation/ref-manual/classes.rst               |    2 +-
 documentation/ref-manual/faq.rst                   |    2 +-
 documentation/ref-manual/features.rst              |    2 +-
 documentation/ref-manual/release-process.rst       |   39 +
 documentation/ref-manual/variables.rst             |   10 +-
 documentation/security-manual/index.rst            |   19 +
 documentation/security-manual/intro.rst            |   28 +
 .../read-only-rootfs.rst                           |    0
 .../securing-images.rst                            |   20 +-
 .../vulnerabilities.rst                            |    0
 documentation/security-reference/index.rst         |   14 +
 .../reporting-vulnerabilities.rst                  |   85 ++
 documentation/security-reference/security-team.rst |  110 ++
 documentation/test-manual/ptest.rst                |   19 +
 32 files changed, 1318 insertions(+), 1979 deletions(-)
 delete mode 100644 diagrams/poky-buildprocess/Pokyarch_diag.jpg
 delete mode 100644 diagrams/poky-buildprocess/Pokyarch_diag.svg
 delete mode 100644 diagrams/poky-buildprocess/Pokyarch_diag2.svg
 delete mode 100644 diagrams/poky-buildprocess/pokyarch4.dia
 delete mode 100644 diagrams/poky-buildprocess/pokyarch4.png
 delete mode 100644 documentation/dev-manual/security-subjects.rst
 delete mode 100644 documentation/overview-manual/figures/YP-flow-diagram.png
 create mode 100644 documentation/overview-manual/svg/yp-flow-diagram.svg
 create mode 100644 documentation/security-manual/index.rst
 create mode 100644 documentation/security-manual/intro.rst
 rename documentation/{dev-manual => security-manual}/read-only-rootfs.rst (100%)
 rename documentation/{dev-manual => security-manual}/securing-images.rst (88%)
 rename documentation/{dev-manual => security-manual}/vulnerabilities.rst (100%)
 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


             reply	other threads:[~2026-01-13  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  9:54 Antonin Godard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-02 14:38 [whinlatter] Pull request Antonin Godard
2026-03-25 10:48 Antonin Godard
2026-03-05 17:13 Antonin Godard
2026-02-27 10:00 Antonin Godard
2026-02-11 14:40 Antonin Godard
2026-01-30  9:35 Antonin Godard
2025-12-24  9:04 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=DFNDCBAFKMQ0.1SZFJLNOJEVLX@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