From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Talel BELHADJ SALEM" <bhstalel@gmail.com>
Cc: <docs@lists.yoctoproject.org>
Subject: Re: [docs][PATCH 1/2] ref-manual/classes.rst: add details about actions done by base.bbclass
Date: Tue, 23 Sep 2025 18:15:40 +0200 [thread overview]
Message-ID: <DD0BBH0D637J.242PE62ZN7FPV@bootlin.com> (raw)
In-Reply-To: <CAOgG7m0qPUsyWcDmvfTggN7_=cKfmOKQtQ_A7OMCFDtjSd6wXw@mail.gmail.com>
On Mon Sep 22, 2025 at 8:12 PM CEST, Talel BELHADJ SALEM wrote:
> I will wait for your review on the 2/2 patch before submitting v2.
>
> Kind Regards
> Talel
Feel free to send the first one separately. It's not strictly related to the
second one if I understood correctly.
Reviewing the diagram will take a bit more time.
One remark I just had is that we would need to stick with the Yocto Project
color scheme, fonts, etc. See:
https://git.yoctoproject.org/yocto-docs/tree/documentation/standards.md#n173
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-09-23 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-21 16:43 [docs][PATCH 0/2] Add more details about the behaviour of the base class Talel BELHAJ SALEM
2025-09-21 16:43 ` [docs][PATCH 1/2] ref-manual/classes.rst: add details about actions done by base.bbclass Talel BELHAJ SALEM
2025-09-22 14:32 ` Antonin Godard
2025-09-22 18:05 ` Talel BELHADJ SALEM
[not found] ` <1867ACF8FB1FE7F2.23261@lists.yoctoproject.org>
2025-09-22 18:12 ` Talel BELHADJ SALEM
2025-09-23 16:15 ` Antonin Godard [this message]
2025-09-25 14:55 ` Talel BELHADJ SALEM
2025-09-25 15:11 ` Antonin Godard
2025-09-21 16:43 ` [docs][PATCH 2/2] ref-manual/classes.rst: add diagram for classes used " Talel BELHAJ SALEM
2025-09-25 14:29 ` Antonin Godard
2025-09-25 18:00 ` Gyorgy Sarvari
2025-09-30 11:18 ` Talel BELHADJ SALEM
2025-10-02 8:06 ` 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=DD0BBH0D637J.242PE62ZN7FPV@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=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 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.