From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antonin Godard <antonin.godard@bootlin.com>,
Paul Eggleton <bluelightning@bluelightning.org>
Subject: [PATCH v2 0/2] Move devtool doc from extensible to dev manual
Date: Thu, 02 Jan 2025 10:40:41 +0100 [thread overview]
Message-ID: <20250102-devtool-dev-manual-v2-0-db3fcb81b938@bootlin.com> (raw)
[ YOCTO #13417 ]
As described in https://bugzilla.yoctoproject.org/show_bug.cgi?id=13417,
the devtool documentation is not really coupled to the extensible SDK,
and so documentation for it could be part of its own manual in the
dev-manual.
The first patch of the series moves the documentation from
sdk-manual/extensible.rst to dev-manual/index.rst. The second patch
removes some reference to the eSDK in the manual which no longer apply
within this new context.
This series depends on:
https://lore.kernel.org/r/20241223-devtool-deploy-target-v1-1-ee00beb47691@bootlin.com
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
Changes in v2:
- forgot to fix some references to titles in the previous version, fixed
them in this v2.
- Link to v1: https://lore.kernel.org/r/20241224-devtool-dev-manual-v1-0-0cc4fb584018@bootlin.com
---
Antonin Godard (2):
Move devtool doc from extensible to dev manual
dev-manual/devtool: remove reference to the extensible SDK
documentation/dev-manual/devtool.rst | 954 ++++++++++++++++++++
.../figures/devtool-add-flow.png} | Bin
.../figures/devtool-modify-flow.png} | Bin
.../figures/devtool-upgrade-flow.png} | Bin
documentation/dev-manual/index.rst | 1 +
documentation/sdk-manual/extensible.rst | 959 +--------------------
6 files changed, 960 insertions(+), 954 deletions(-)
---
base-commit: 4b904539d05fdac123ed96c3952613fbbe612c39
change-id: 20241223-devtool-dev-manual-bb387251f9be
prerequisite-change-id: 20241223-devtool-deploy-target-27d9f6e8a250:v1
prerequisite-patch-id: d3a98c5a92ce8ed4945595df218769028f552057
Best regards,
--
Antonin Godard <antonin.godard@bootlin.com>
next reply other threads:[~2025-01-02 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 9:40 Antonin Godard [this message]
2025-01-02 9:40 ` [PATCH v2 1/2] Move devtool doc from extensible to dev manual Antonin Godard
2025-01-02 9:40 ` [PATCH v2 2/2] dev-manual/devtool: remove reference to the extensible SDK Antonin Godard
2025-01-09 21:55 ` [docs] [PATCH v2 0/2] Move devtool doc from extensible to dev manual Adrian Freihofer
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=20250102-devtool-dev-manual-v2-0-db3fcb81b938@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=bluelightning@bluelightning.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox