From: "Markus Volk" <f_l_k@t-online.de>
To: Ross Burton <Ross.Burton@arm.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 5/5] go-mod-update-modules: include the generated files from the class
Date: Fri, 25 Sep 2026 18:27:06 +0200 [thread overview]
Message-ID: <7PHXLT.V9NSMKKNGKOU@t-online> (raw)
In-Reply-To: <776C7C9B-D450-4067-B9E0-A68576F303A3@arm.com>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
On Fri, Sep 25 2026 at 11:18:39 +00:00:00, Ross Burton
<Ross.Burton@arm.com> wrote:
> Where is this new recipe coming from? recipetool should be creating
> the files when it writes the recipe file so it canā€™t be there. If
> youā€™re hand-coding the recipe then you can touch the files when you
> write require, or just include in the recipe.
Hi Ross,
the recipe was hand-coded and I wasn't aware that recipetool creates
the files. You definitely got a point here
[-- Attachment #2: Type: text/html, Size: 658 bytes --]
next prev parent reply other threads:[~2026-09-25 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 9:23 [oe-core][PATCH 1/5] gcr: initialize libgcrypt from the secret exchange Markus Volk
2026-09-22 9:23 ` [oe-core][PATCH 2/5] cpan: survive the Makefile that MakeMaker rebuilds under us Markus Volk
2026-09-26 14:05 ` Paul Barker
2026-09-26 19:03 ` Markus Volk
2026-09-22 9:23 ` [oe-core][PATCH 3/5] spdx_license: give UnknownId a name Markus Volk
2026-09-22 9:23 ` [oe-core][PATCH 4/5] license_finder: normalise license texts before hashing Markus Volk
2026-09-22 9:23 ` [oe-core][PATCH 5/5] go-mod-update-modules: include the generated files from the class Markus Volk
2026-09-22 14:14 ` Antonin Godard
2026-09-23 17:23 ` mrksvolk
2026-09-23 18:03 ` Khem Raj
2026-09-25 11:18 ` Ross Burton
2026-09-25 16:27 ` Markus Volk [this message]
2026-09-22 9:33 ` Patchtest results for [oe-core][PATCH 1/5] gcr: initialize libgcrypt from the secret exchange patchtest
2026-09-26 13:53 ` Paul Barker
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=7PHXLT.V9NSMKKNGKOU@t-online \
--to=f_l_k@t-online.de \
--cc=Ross.Burton@arm.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 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.