From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 4/6] dev-manual/multiconfig: rename to use Multiconfig term
Date: Tue, 11 Feb 2025 12:02:59 +0100 [thread overview]
Message-ID: <76021de4-0b41-4b91-a73e-3690a90bdc7e@cherry.de> (raw)
In-Reply-To: <20250207-multiconfig-doc-v1-4-f63cdab1fad9@bootlin.com>
Hi Antonin,
On 2/7/25 5:28 PM, Antonin Godard via lists.yoctoproject.org wrote:
> Rename this section to explicitely name the multiple configuration feature
> "multiconfig".
>
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Thanks!
Quentin
next prev parent reply other threads:[~2025-02-11 11:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 16:28 [PATCH 0/6] Improve multiconfig documentation Antonin Godard
2025-02-07 16:28 ` [PATCH 1/6] dev-manual: move multiconfig documentation to its own document Antonin Godard
2025-02-11 10:41 ` [docs] " Quentin Schulz
2025-02-11 11:02 ` Quentin Schulz
2025-02-07 16:28 ` [PATCH 2/6] variables.rst: add a reference to BB_CURRENT_MC from bbdocs Antonin Godard
2025-02-11 10:52 ` [docs] " Quentin Schulz
2025-02-07 16:28 ` [PATCH 3/6] migration-5.2: fix references to BB_CURRENT_MC Antonin Godard
2025-02-07 16:28 ` [PATCH 4/6] dev-manual/multiconfig: rename to use Multiconfig term Antonin Godard
2025-02-11 11:02 ` Quentin Schulz [this message]
2025-02-07 16:28 ` [PATCH 5/6] dev-manual/multiconfig: improve the current doc Antonin Godard
2025-02-11 11:19 ` [docs] " Quentin Schulz
2025-02-12 12:49 ` Antonin Godard
2025-02-17 11:34 ` Quentin Schulz
2025-02-07 16:28 ` [PATCH 6/6] dev-manual/multiconfig: add suggested best practices and baremetal sections Antonin Godard
2025-02-11 12:08 ` [docs] " Quentin Schulz
2025-02-12 12:49 ` 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=76021de4-0b41-4b91-a73e-3690a90bdc7e@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=antonin.godard@bootlin.com \
--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 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.