public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: Antonin Godard <antonin.godard@bootlin.com>,
	bitbake-devel@lists.openembedded.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] doc: extend classes and include/require documentation
Date: Mon, 12 Jan 2026 17:38:00 +0100	[thread overview]
Message-ID: <eeec9ff6-d7a0-4f0b-a771-2cc02dbd1cc3@cherry.de> (raw)
In-Reply-To: <DEPGLUKGZXSZ.1CSSAYH72Y1IB@bootlin.com>

Hi Antonin,

On 12/4/25 2:16 PM, Antonin Godard wrote:
> Hi,
> 
> On Wed Dec 3, 2025 at 5:55 PM CET, Quentin Schulz via lists.yoctoproject.org wrote:
> [...]
>> I think we should provide an example for include_all directive as well?
>> After reading the code, I believe include_all does NOT search the local
>> path first, it only searches paths in BBPATH so I think it's worth
>> providing an example and maybe notes on how it differs from the other
>> directives.
>>
>> What do you think?
> 
> That's a good point I forgot here, yes, we should explain it to be complete.
> Can you send a patch of file a bug?
> 

Finally took the time to write a patch, see

https://lore.kernel.org/yocto-docs/20260112-doc-directives-v1-8-b23923cfce89@cherry.de/

Cheers,
Quentin


      reply	other threads:[~2026-01-12 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18 12:16 [PATCH] doc: extend classes and include/require documentation Antonin Godard
2025-12-03 16:55 ` [docs] " Quentin Schulz
2025-12-04 13:16   ` Antonin Godard
2026-01-12 16:38     ` Quentin Schulz [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=eeec9ff6-d7a0-4f0b-a771-2cc02dbd1cc3@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=antonin.godard@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox