From: "BELHADJ SALEM Talel" <bhstalel@gmail.com>
To: docs@lists.yoctoproject.org
Subject: Re: Yocto Tasks Detailed Diagram Proposal
Date: Tue, 17 Oct 2023 11:56:55 -0700 [thread overview]
Message-ID: <29645.1697569015596670723@lists.yoctoproject.org> (raw)
In-Reply-To: <18651.1687433672747999997@lists.yoctoproject.org>
[-- Attachment #1.1: Type: text/plain, Size: 674 bytes --]
Hello,
Returning to the detailed diagram proposal,
I have created another one that is more and more detailed using draw.io, I tried inkspace but it seems really to deal with.
If this SVG file fine and accepted we can move on with it, otherwise, what is the solution for this ? Should I try to take more time to adapt it to inkscape and following the SVG template or someone can help me with this ?
After dealing with that, I am planning to suggest adding a new "6.5 Tasks Map" in ref-manual/tasks and for the recipes example in the diagram I will put their content in that section before introducing the diagram.
What do you think?
Kind Regards,
Talel
[-- Attachment #1.2: Type: text/html, Size: 730 bytes --]
[-- Attachment #2: bitbake_tasks_map.svg --]
[-- Type: image/svg+xml, Size: 194558 bytes --]
[-- Attachment #3: bitbake_tasks_map.png --]
[-- Type: image/png, Size: 3203447 bytes --]
next prev parent reply other threads:[~2023-10-17 18:57 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 ` [docs] " Michael Opdenacker
2023-06-22 9:08 ` Quentin Schulz
2023-06-22 11:34 ` BELHADJ SALEM Talel
2023-10-17 18:56 ` BELHADJ SALEM Talel [this message]
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=29645.1697569015596670723@lists.yoctoproject.org \
--to=bhstalel@gmail.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