All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: docs@lists.yoctoproject.org, Quentin Schulz <foss@0leil.net>
Subject: Re: [docs] [PATCH] ref-manual: remove unused example recipe source files
Date: Mon, 2 Aug 2021 18:16:01 +0200	[thread overview]
Message-ID: <a09495b1-a515-269d-b4d0-4e363ef530fb@bootlin.com> (raw)
In-Reply-To: <16969F1E09D6E656.27324@lists.yoctoproject.org>


On 7/30/21 6:41 PM, Michael Opdenacker wrote:
> Hi Richard,
>
> On 7/29/21 3:48 PM, Richard Purdie wrote:
>>> While I had no problem moving and testing the "hello-single",
>>> "hello-autotools"  (GNU hello actually) and "libxpm" recipe examples,
>>> I'm struggling with the "mtd-utils" one.
>>>
>>> Neither the example recipe (version 1.0.0:
>>> http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/tree/documentation/ref-manual/examples/mtd-makefile/mtd-utils_1.0.0.bb)
>>> nor the one which source code is directly in the documentation (version
>>> 1.5.1+:
>>> http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/tree/documentation/dev-manual/common-tasks.rst#n2307)
>>> compile any more.
>>>
>>> Given that we have an upstream mtd-utils recipe that works, what's the
>>> point of trying to fix a broken example? This seems like a waste of
>>> effort to me...
>>>
>>> So, may I drop that old mtd-utils example?
>> I'd say yes, that one isn't adding value.
> Thanks for confirming this.
>
> I'm waiting for you to merge my oe-core patch
> (https://lists.openembedded.org/g/openembedded-core/message/154245) to
> remove these examples from the documentation.


This is done now (thanks Richard!).
The description of this change has been updated and the commit is in
master-next now.

Cheers,
Michael.

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


  parent reply	other threads:[~2021-08-02 16:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16959EEB5BD85597.12821@lists.yoctoproject.org>
2021-07-27 10:29 ` [docs] [PATCH] ref-manual: remove unused example recipe source files Michael Opdenacker
2021-07-27 11:23   ` Quentin Schulz
2021-07-27 11:38     ` Richard Purdie
2021-07-27 12:36       ` Michael Opdenacker
     [not found]       ` <1695A60376DC3ECA.18160@lists.yoctoproject.org>
2021-07-28 13:56         ` Michael Opdenacker
2021-07-29 13:48           ` Richard Purdie
2021-07-30 16:41             ` Michael Opdenacker
     [not found]             ` <16969F1E09D6E656.27324@lists.yoctoproject.org>
2021-08-02 16:16               ` Michael Opdenacker [this message]
     [not found]         ` <1695F8F487052006.29235@lists.yoctoproject.org>
2021-07-29 13:39           ` Michael Opdenacker

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=a09495b1-a515-269d-b4d0-4e363ef530fb@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=foss@0leil.net \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.