From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Luca Bocassi <luca.boccassi@gmail.com>,
openembedded-core@lists.openembedded.org
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [OE-core] [PATCH 2/2] mount-copybind: add MOUNT_COPYBIND_AVOID_OVERLAYFS env var to skip OverlayFS
Date: Mon, 28 Mar 2022 18:08:18 +0200 [thread overview]
Message-ID: <1f6c9456-2896-2e60-7dfe-b88420cf97c3@bootlin.com> (raw)
In-Reply-To: <0b46c32fb91e47f1e561a29d323f231bc59684c1.camel@debian.org>
Hi Luca,
On 3/28/22 17:32, Luca Bocassi wrote:
>
>> Thanks for the patch!
>> Now that the patch is merged, would you mind proposing a patch to add a
>> description of it to the documentation? You'll probably do it better
>> than I would.
>>
>> Thanks in advance
>> Michael.
> Sure I can do that, where should it be listed exactly?
Great!
Well, I was thinking about adding an entry to
https://git.yoctoproject.org/yocto-docs/tree/documentation/ref-manual/variables.rst
corresponding to https://docs.yoctoproject.org/ref-manual/variables.html
However, I'm starting to have doubts as "volatile-binds" are not even
documented. Is this new variable meant to be used in the configuration
file? If so, it probably needs documenting, but it's nice when a
variable is either attached to a bbclass or is introduced in one of the
manuals too.
Ideas anyone?
Thanks again
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-03-28 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 18:40 [PATCH 1/2] mount-copybind: fix shellcheck warning luca.boccassi
2022-03-25 18:40 ` [PATCH 2/2] mount-copybind: add MOUNT_COPYBIND_AVOID_OVERLAYFS env var to skip OverlayFS luca.boccassi
2022-03-28 15:30 ` [OE-core] " Michael Opdenacker
2022-03-28 15:32 ` Luca Boccassi
2022-03-28 16:08 ` Michael Opdenacker [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=1f6c9456-2896-2e60-7dfe-b88420cf97c3@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=luca.boccassi@gmail.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