public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [kirkstone][PATCH 00/10] kirkstone backports
Date: Wed, 20 Sep 2023 10:15:34 +0200	[thread overview]
Message-ID: <20230920081544.1226760-1-michael.opdenacker@bootlin.com> (raw)

From: Michael Opdenacker <michael.opdenacker@bootlin.com>

From now on, will apply such backports more systematically,
in a single branch rather than individually, and only after changes are merged
in master, though exceptions for urgent cases could still be made.

Michael Opdenacker (9):
  sdk-manual: extensible.rst: align with master branch
  dev-manual: disk-space: improve wording for obsolete sstate cache
    files
  documentation/README: align with master
  dev-manual: new-recipe.rst fix inconsistency with contributor guide
  contributor-guide: recipe-style-guide: add Upstream-Status
  dev-manual: licenses: mention SPDX for license compliance
  ref-manual: qa-checks: align with master
  manuals: document "mime-xdg" class and MIME_XDG_PACKAGES
  dev-manual: licenses: update license manifest location

Roland Hieber (1):
  template: fix typo in section header

 documentation/README                          |  43 +-
 .../contributor-guide/recipe-style-guide.rst  |  81 ++++
 documentation/dev-manual/disk-space.rst       |   8 +-
 documentation/dev-manual/licenses.rst         |  35 +-
 documentation/dev-manual/new-recipe.rst       |  13 +-
 .../migration-guides/migration-3.1.rst        |   2 +-
 documentation/ref-manual/classes.rst          |  21 +
 documentation/ref-manual/qa-checks.rst        |  87 ++--
 documentation/ref-manual/variables.rst        |   7 +
 documentation/sdk-manual/extensible.rst       | 389 +++++++++---------
 documentation/template/template.svg           |   2 +-
 11 files changed, 448 insertions(+), 240 deletions(-)

-- 
2.34.1



             reply	other threads:[~2023-09-20  8:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  8:15 michael.opdenacker [this message]
2023-09-20  8:15 ` [kirkstone][PATCH 01/10] sdk-manual: extensible.rst: align with master branch michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 02/10] dev-manual: disk-space: improve wording for obsolete sstate cache files michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 03/10] documentation/README: align with master michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 04/10] dev-manual: new-recipe.rst fix inconsistency with contributor guide michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 05/10] contributor-guide: recipe-style-guide: add Upstream-Status michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 06/10] dev-manual: licenses: mention SPDX for license compliance michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 07/10] template: fix typo in section header michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 08/10] ref-manual: qa-checks: align with master michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 09/10] manuals: document "mime-xdg" class and MIME_XDG_PACKAGES michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 10/10] dev-manual: licenses: update license manifest location 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=20230920081544.1226760-1-michael.opdenacker@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.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