public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Mingrui Ren <jiladahe1997@gmail.com>, docs@lists.yoctoproject.org
Cc: foss@0leil.net, 972931182@qq.com
Subject: Re: [docs] [PATCH] dev-manual: fix wrong file
Date: Wed, 28 Jul 2021 17:41:47 +0200	[thread overview]
Message-ID: <40389349-3aab-cd16-3fe1-69b770358c54@bootlin.com> (raw)
In-Reply-To: <45f034b6-c943-de00-86a7-dfce48cbffa9@gmail.com>

Greetings,

Apologies for the late reply!

On 6/21/21 4:33 PM, Mingrui Ren wrote:
> From 43e67b6c7c5e29d608b5459c6041b195ac94e4cc Mon Sep 17 00:00:00 2001
> From: Mingrui Ren <jiladahe1997@gmail.com>
> Date: Mon, 21 Jun 2021 21:38:45 +0800
> Subject: [PATCH] dev-manual: fix wrong file
>
> The file 'meta/classes/core-image.bbclass' seems have nothing about
> 'IMAGE_FEATURES' variable, maybe it should be
> 'meta/classes/image.bbclass'.
>
> Signed-off-by: Mingrui Ren <jiladahe1997@gmail.com>
> ---
>  documentation/dev-manual/common-tasks.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/documentation/dev-manual/common-tasks.rst
> b/documentation/dev-manual/common-tasks.rst
> index 762636a17c..9ff33a4ce8 100644
> --- a/documentation/dev-manual/common-tasks.rst
> +++ b/documentation/dev-manual/common-tasks.rst
> @@ -872,7 +872,7 @@ a recipe and using :term:`EXTRA_IMAGE_FEATURES`
> from within your
>  :term:`Build Directory`.
>
>  To understand how these features work, the best reference is
> -``meta/classes/core-image.bbclass``. This class lists out the available
> +``meta/classes/image.bbclass``. This class lists out the available
>  :term:`IMAGE_FEATURES` of which most map to package groups while
> some, such
>  as ``debug-tweaks`` and ``read-only-rootfs``, resolve as general
>  configuration settings.

Thanks for reporting this. I agree with your proposal.

I couldn't apply the patch with "git am", but I recreated it manually.
It's now in the "master-next"  branch of "yocto-docs" and should be in
"master" (in the public documentation) in the next days.

Thanks again!
Cheers,
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2021-07-28 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 14:33 [PATCH] dev-manual: fix wrong file Mingrui Ren
2021-07-28 15:41 ` 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=40389349-3aab-cd16-3fe1-69b770358c54@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=972931182@qq.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=foss@0leil.net \
    --cc=jiladahe1997@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