public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Bel Hadj Salem Talel <talel.hajsalem@sofia-technologies.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] Yocto Tasks Detailed Diagram Proposal
Date: Tue, 1 Nov 2022 16:42:17 +0100	[thread overview]
Message-ID: <898edb5f-3e7c-9763-c84f-6b59fb5daef6@bootlin.com> (raw)
In-Reply-To: <3u6w.1667236384580014962.DpiY@lists.yoctoproject.org>

Hi Talel

On 10/31/22 18:13, Bel Hadj Salem Talel wrote:
> Hello All,
>
> I did create a detailed diagram about Yocto Tasks and where they 
> happen exactly in tmp, downloads and other directories in the build 
> folder.
>
> Please find attached the SVG diagram.
>
> If it can be added to Yocto documentation it would be great, so any 
> comments/reviews are welcome.
>
> This will setup the way for me to add more detailed diragrams about 
> other Yocto topics.


Many thanks for proposing this contribution!
Before we find a place in the manual where we could use it, I've got an 
issue with the text labels, which Google docs turned into shapes when 
you exported to SVG, removing the possibility to edit them in the future.

Ultimately, I'd like this diagram to be maintained in SVG format, so 
that everyone can easily maintain them, typically using Inkscape.

Maybe we can manually edit this SVG document to fix this, replacing the 
shapes by real text, which could be rather quick.

List members, any feedback about the content itself?

Thanks again
Michael.

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



  reply	other threads:[~2022-11-01 15:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 17:13 Yocto Tasks Detailed Diagram Proposal Bel Hadj Salem Talel
2022-11-01 15:42 ` Michael Opdenacker [this message]
2023-06-22  9:08   ` [docs] " Quentin Schulz
2023-06-22 11:34     ` BELHADJ SALEM Talel
2023-10-17 18:56       ` BELHADJ SALEM Talel
2023-10-19 14:29         ` [docs] " Michael Opdenacker
2023-10-20 18:03           ` Talel BELHADJ SALEM
2023-10-27  8:17             ` Michael Opdenacker
2023-10-27 12:18               ` Talel BELHADJ SALEM
2023-10-27 15:02                 ` Michael Opdenacker
2023-10-27 15:31                   ` Talel BELHADJ SALEM
     [not found]           ` <178FE2DDDBFED311.11247@lists.yoctoproject.org>
2023-10-27  7:27             ` Talel BELHADJ SALEM

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=898edb5f-3e7c-9763-c84f-6b59fb5daef6@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=talel.hajsalem@sofia-technologies.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