From: Ross Burton <Ross.Burton@arm.com>
To: "liuyd.fnst@fujitsu.com" <liuyd.fnst@fujitsu.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH 6/6] orc: Enable hotdoc to produce doc
Date: Thu, 5 Feb 2026 14:06:07 +0000 [thread overview]
Message-ID: <0348A260-53CF-412B-9714-53D26703C504@arm.com> (raw)
In-Reply-To: <20260129035353.8982-7-liuyd.fnst@fujitsu.com>
On 29 Jan 2026, at 03:53, Yiding Liu (Fujitsu) via lists.openembedded.org <liuyd.fnst=fujitsu.com@lists.openembedded.org> wrote:
> +DEPENDS = "hotdoc-native"
We have an api-documentation DISTRO_FEATURE, please respect that.
Ross
prev parent reply other threads:[~2026-02-05 14:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 3:53 [PATCH 0/6] Investigate hotdoc and add a recipe to build it Liu Yiding
2026-01-29 3:53 ` [OE-core][PATCH 1/6] python3-appdirs: Add new recipe Liu Yiding
2026-01-30 8:28 ` Mathieu Dubois-Briand
2026-01-30 21:36 ` Mathieu Dubois-Briand
2026-01-29 3:53 ` [OE-core][PATCH 2/6] python3-schema: " Liu Yiding
2026-01-29 3:53 ` [OE-core][PATCH 3/6] python3-toposort: " Liu Yiding
2026-01-29 3:53 ` [OE-core][PATCH 4/6 v2] python3-wheezy-template: " Liu Yiding
2026-01-29 3:53 ` [OE-core][PATCH 5/6 v3] hotdoc: " Liu Yiding
2026-01-29 3:53 ` [OE-core][PATCH 6/6] orc: Enable hotdoc to produce doc Liu Yiding
2026-01-29 4:01 ` Patchtest results for " patchtest
2026-01-29 11:26 ` Alexander Kanavin
2026-01-30 2:19 ` 回复: " Yiding Liu (Fujitsu)
2026-02-05 2:59 ` Yiding Liu (Fujitsu)
2026-02-05 9:50 ` Alexander Kanavin
2026-02-10 2:41 ` 回复: " Yiding Liu (Fujitsu)
2026-02-10 9:41 ` Alexander Kanavin
2026-02-11 2:35 ` 回复: " Yiding Liu (Fujitsu)
2026-02-11 11:47 ` Alexander Kanavin
2026-02-12 2:16 ` 回复: " Yiding Liu (Fujitsu)
2026-02-12 11:42 ` Alexander Kanavin
2026-02-05 14:06 ` Ross Burton [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=0348A260-53CF-412B-9714-53D26703C504@arm.com \
--to=ross.burton@arm.com \
--cc=liuyd.fnst@fujitsu.com \
--cc=openembedded-core@lists.openembedded.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