From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <adrian.freihofer@siemens.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH v3 4/4] dev-manual/devtool: convert add/modify/upgrade flow diagrams to Mermaid
Date: Fri, 16 Oct 2026 14:32:39 +0200 [thread overview]
Message-ID: <DM69K3AOTBE3.2F8QLMXMKK75Q@bootlin.com> (raw)
In-Reply-To: <20261015200726.2391599-5-adrian.freihofer@siemens.com>
On Thu Oct 15, 2026 at 10:06 PM CEST, Adrian Freihofer via lists.yoctoproject.org wrote:
> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
> Replace the devtool-add-flow.png, devtool-modify-flow.png and
> devtool-upgrade-flow.png diagrams with Mermaid (.mmd) flowcharts and
> their pre-rendered SVGs, in the same style as the ide-sdk diagrams
> added in the previous commit. The PNGs are removed since they are no
> longer referenced.
>
> The add and modify diagrams also gain a "devtool ide-sdk" branch,
> showing it as an alternative to the manual build/deploy-target loop.
>
> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> ---
> documentation/dev-manual/devtool.rst | 12 +-
> .../dev-manual/figures/devtool-add-flow.mmd | 104 +++++++++++++++++
I don't think it is necessary to keep the mmd files (see why patch 3/4).
> .../dev-manual/figures/devtool-add-flow.png | Bin 181699 -> 0 bytes
> .../dev-manual/figures/devtool-add-flow.svg | 1 +
> .../figures/devtool-modify-flow.mmd | 108 ++++++++++++++++++
> .../figures/devtool-modify-flow.png | Bin 171676 -> 0 bytes
> .../figures/devtool-modify-flow.svg | 1 +
For this one and the devtool add one, wouldn't it be more correct to have the
"devtool ide-sdk recipe image" before "Edit source code"?
Thanks,
Antonin
prev parent reply other threads:[~2026-10-16 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 20:06 [PATCH v3 0/4] dev-manual/devtool: ide-sdk doc rewrite and Mermaid diagrams AdrianF
2026-10-15 20:06 ` [PATCH v3 1/4] dev-manual/devtool: fix non-patch local file handling docs AdrianF
2026-10-16 12:32 ` [docs] " Antonin Godard
2026-10-15 20:06 ` [PATCH v3 2/4] dev-manual/devtool: update devtool ide-sdk section for recent features AdrianF
2026-10-16 12:32 ` [docs] " Antonin Godard
2026-10-15 20:06 ` [PATCH v3 3/4] dev-manual/devtool: add diagrams for the ide-sdk workflow and architecture AdrianF
2026-10-16 12:32 ` [docs] " Antonin Godard
[not found] ` <20261015200726.2391599-5-adrian.freihofer@siemens.com>
2026-10-16 12:32 ` Antonin Godard [this message]
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=DM69K3AOTBE3.2F8QLMXMKK75Q@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=adrian.freihofer@siemens.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