All of lore.kernel.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: [scarthgap] Pull request
Date: Mon, 13 Oct 2025 18:36:02 +0200	[thread overview]
Message-ID: <DDHC9YABOE71.1XI9SF9SH8ZP0@bootlin.com> (raw)

The following changes since commit 6f086fd3d9dbbb0c80f6c3e89b8df4fed422e79a:

  ref-manual/variables.rst: fix the description of STAGING_DIR (2025-10-03 11:49:14 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 6cd7492bf83232744390f34e496367e94b63e701:

  vulnerabilities: update nvdcve file name (2025-10-13 09:13:32 +0200)

----------------------------------------------------------------
Lee Chee Yang (1):
      migration-guides: add release notes for 4.0.30

Peter Marko (1):
      vulnerabilities: update nvdcve file name

 documentation/dev-manual/vulnerabilities.rst       |   2 +-
 documentation/migration-guides/release-4.0.rst     |   1 +
 .../migration-guides/release-notes-4.0.30.rst      | 170 +++++++++++++++++++++
 3 files changed, 172 insertions(+), 1 deletion(-)
 create mode 100644 documentation/migration-guides/release-notes-4.0.30.rst


             reply	other threads:[~2025-10-13 16:36 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 16:36 Antonin Godard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-19 13:51 [scarthgap] Pull request Antonin Godard
2026-04-27  8:30 Antonin Godard
2026-04-21 13:44 Antonin Godard
2026-04-22  9:37 ` Paul Barker
2026-04-16 12:41 Antonin Godard
2026-04-16 13:35 ` Paul Barker
2026-04-02 14:38 Antonin Godard
2026-03-30  8:42 Antonin Godard
2026-03-31  8:15 ` Paul Barker
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
2026-01-13  9:54 Antonin Godard
2025-12-24  9:04 Antonin Godard
2025-12-11 10:23 Antonin Godard
2025-11-14 17:16 Antonin Godard
2025-10-29  8:36 Antonin Godard
2025-10-20  7:27 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
2025-03-21 10:40 Antonin Godard
2025-03-07 16:37 Antonin Godard
2025-02-25 16:56 Antonin Godard
2025-02-14 13:27 Antonin Godard
2025-02-07  9:03 Antonin Godard
2025-01-27 15:58 Antonin Godard
2025-01-20  8:39 Antonin Godard
2025-01-08 16:00 Antonin Godard
2024-12-27 14:02 Antonin Godard
2024-12-20  8:46 Antonin Godard
2024-12-16  8:24 Antonin Godard
2024-11-29  8:07 Antonin Godard
2024-11-15  8:04 Antonin Godard
2024-11-06 15:48 Antonin Godard
2024-10-31 12:47 Antonin Godard
2024-10-25  8:37 Antonin Godard
2024-10-18  7:33 Antonin Godard
2024-10-08 13:48 Alexandre Belloni
2024-09-09  7:17 Alexandre Belloni
2024-08-22  9:36 Alexandre Belloni
2024-07-26 21:08 Alexandre Belloni
2024-06-27 16:29 Alexandre Belloni

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=DDHC9YABOE71.1XI9SF9SH8ZP0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.