From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
"docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCHv3] ref-manual: Add documentation of PACKAGE_DEBUG_FILE_SUFFIX
Date: Mon, 10 Jan 2022 16:18:12 +0100 [thread overview]
Message-ID: <f15b0092-5311-e8a6-6fe1-e7ee0c191674@bootlin.com> (raw)
In-Reply-To: <1057c8a51923484cb72ca4fc813d68c1@axis.com>
On 1/10/22 3:52 PM, Peter Kjellerstedt wrote:
>
> Just be aware that it still hasn't made it into meta...
Oops, I removed it from master-next then.
Just keep me posted when the corresponding patch is merged.
Thanks
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2022-01-10 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 17:04 [PATCHv3] ref-manual: Add documentation of PACKAGE_DEBUG_FILE_SUFFIX Peter Kjellerstedt
2022-01-10 14:39 ` [docs] " Michael Opdenacker
2022-01-10 14:52 ` Peter Kjellerstedt
2022-01-10 15:18 ` 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=f15b0092-5311-e8a6-6fe1-e7ee0c191674@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=peter.kjellerstedt@axis.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