From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
"YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] ref-manual: organize all recipes-* directories under subdirectory
Date: Thu, 25 Jun 2026 10:01:15 +0200 [thread overview]
Message-ID: <DJHZ0Q6RNWE3.4CJ8FWBSSANU@bootlin.com> (raw)
In-Reply-To: <543708dc-e1aa-0798-653b-d8c073dbec50@crashcourse.ca>
Hi,
On Mon Jun 22, 2026 at 10:29 PM CEST, Robert P. J. Day wrote:
>
> It's cumbersome to list all meta/recipes-* directories under the same
> level as other meta/ directories, so place them under a recipes-*
> higher-level directory.
I disagree. I don't see the added value of this, and following this logic you'd
have to do this for conf/ as well. I think it would just add too many levels of
headers.
Antonin
next prev parent reply other threads:[~2026-06-25 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 20:29 [PATCH] ref-manual: organize all recipes-* directories under subdirectory Robert P. J. Day
2026-06-25 8:01 ` Antonin Godard [this message]
2026-06-25 8:02 ` [docs] " Robert P. J. Day
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=DJHZ0Q6RNWE3.4CJ8FWBSSANU@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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;
as well as URLs for NNTP newsgroup(s).