From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Cc: Tim Orling <ticotimo@gmail.com>
Subject: Documenting VIRTUAL-RUNTIME variables
Date: Tue, 5 Mar 2024 15:51:33 +0100 [thread overview]
Message-ID: <93bfc62e-c92b-4aff-b06e-40bbcbd46d87@bootlin.com> (raw)
Greetings,
Following a warning from Tim (thanks!).
The VIRTUAL-RUNTIME_* variables do not appear in the YP manual variable
index, and we shouldn't definitely address this.
However, I still hesitate between:
1. Creating multiple entries, especially for the most frequent
variables (VIRTUAL-RUNTIME_init_manager,
VIRTUAL-RUNTIME_dev_manager...), and maybe for "VIRTUAL-RUNTIME" as
a name prefix
2. Creating just a generic "VIRTUAL-RUNTIME" entry for this common prefix.
I'm tempted to go for 1, but then I guess it opens to door to
documenting most uses of this scheme.
Your opinions are welcome!
Thanks
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2024-03-05 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 14:51 Michael Opdenacker [this message]
2024-03-05 14:55 ` [docs] Documenting VIRTUAL-RUNTIME variables Richard Purdie
2024-03-05 17:02 ` Tim Orling
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=93bfc62e-c92b-4aff-b06e-40bbcbd46d87@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=ticotimo@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).