docs.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 19 Sep 2023 16:39:46 +0200	[thread overview]
Message-ID: <bfa5ee5d-206e-9357-c486-73023990d8b3@bootlin.com> (raw)

Hi Richard,

The following changes since commit 7ec90b6af4dc32dbe313b77d17297e19c809bb3c:

   README: Update to point to new contributor guide (2023-09-07 11:27:06 
+0200)

are available in the Git repository at:

   git://git.yoctoproject.org/yocto-docs master-next

for you to fetch changes up to 318261d8ea91c2373709a9c1e82304ab7e9e9a3b:

   sdk-manual: extensible.rst: fix multiple formatting issues 
(2023-09-19 16:31:50 +0200)

----------------------------------------------------------------
Michael Opdenacker (6):
       dev-manual: new-recipe.rst fix inconsistency with contributor guide
       contributor-guide: recipe-style-guide: add Upstream-Status
       dev-manual: licenses: update license manifest location
       dev-manual: licenses: mention SPDX for license compliance
       dev-manual: disk-space: improve wording for obsolete sstate cache 
files
       sdk-manual: extensible.rst: fix multiple formatting issues

Roland Hieber (2):
       template: fix typo in section header
       ref-manual: point outdated link to the new location

Ross Burton (1):
       manuals: document LICENSE_FLAGS_DETAILS

  documentation/contributor-guide/recipe-style-guide.rst |  81 
+++++++++++++++++++++++++++++++++++++++++++++++
  documentation/dev-manual/disk-space.rst                |   8 ++---
  documentation/dev-manual/licenses.rst                  |  42 
+++++++++++++++++++------
  documentation/dev-manual/new-recipe.rst                |  13 ++++----
  documentation/migration-guides/release-notes-4.3.rst   |   5 ++-
  documentation/ref-manual/qa-checks.rst                 |  10 +++---
  documentation/ref-manual/variables.rst                 |  17 ++++++++++
  documentation/sdk-manual/extensible.rst                | 254 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------------------------------
  documentation/template/template.svg                    |   2 +-
  9 files changed, 259 insertions(+), 173 deletions(-)

Thank you in advance
Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



             reply	other threads:[~2023-09-19 14:39 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 14:39 Michael Opdenacker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-22  7:43 [master] Pull request 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-18  9:58 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-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=bfa5ee5d-206e-9357-c486-73023990d8b3@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 NNTP newsgroup(s).