All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH v2 4/5] sdk-manual: rename the section to remove "extensible"
Date: Thu, 6 Aug 2026 10:45:50 +0200	[thread overview]
Message-ID: <d9e8fe7b-349c-43a1-8ff4-188fe4c1f417@cherry.de> (raw)
In-Reply-To: <20260731-sdk-clarifications-v2-4-b34f797492b1@bootlin.com>

Hi Antonin,

On 7/31/26 11:19 AM, Antonin Godard via lists.yoctoproject.org wrote:
> The SDK manual covers both the standard and extensible SDKs yet the
> title does not imply that, so rename the section to "Yocto Project
> Application Development and the Software Development Kit (SDK) Manual".
> 
> As a consequence, rename the first section title and reword the intro.
> 

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin


  reply	other threads:[~2026-08-06 12:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  9:19 [PATCH v2 0/5] Make the SDK section not specific to the eSDK Antonin Godard
2026-07-31  9:19 ` [PATCH v2 1/5] sdk-manual/appendix-customizing-standard.rst: use code block for bitbake assignment Antonin Godard
2026-07-31  9:19 ` [PATCH v2 2/5] sdk-manual/intro.rst: remove a confusing sentence Antonin Godard
2026-07-31  9:19 ` [PATCH v2 3/5] sdk-manual/intro.rst: link to sysroot term Antonin Godard
2026-07-31  9:19 ` [PATCH v2 4/5] sdk-manual: rename the section to remove "extensible" Antonin Godard
2026-08-06  8:45   ` Quentin Schulz [this message]
2026-07-31  9:19 ` [PATCH v2 5/5] sdk-manual/intro.rst: detail differences between standard and extensible sysroots Antonin Godard
2026-08-06  8:48   ` [docs] " Quentin Schulz
2026-08-13 12:01 ` [PATCH v2 0/5] Make the SDK section not specific to the eSDK 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=d9e8fe7b-349c-43a1-8ff4-188fe4c1f417@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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.