From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Paul Barker" <paul@pbarker.dev>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] recipe-style-guide: Clarify when License-Update tag is needed
Date: Fri, 05 Jun 2026 16:05:24 +0200 [thread overview]
Message-ID: <DJ168NAEZ2ZU.ZCFOL92MHAE0@bootlin.com> (raw)
In-Reply-To: <a92e5b037d8da3ea466945b99c6190212c5110ba.camel@pbarker.dev>
On Thu Jun 4, 2026 at 12:18 PM CEST, Paul Barker wrote:
[...]
>> > +The ``License-Update:`` tag is not needed for commits which fix incorrect
>> > +license data in our metadata.
>>
>> By reading this alone I fail to see a use-case, could you provide an example?
>> Perhaps a link to such a commit? (you can use :oecore_rev:`<commit sha>` to
>> create the link).
>
> Hi Antonin,
>
> This was while discussing a series from Joshua [1] and follow-up patches
> from Richard. I can send a v2 shortly once the commits are merged to
> master and mirrors have updated, etc.
>
> [1]: https://lore.kernel.org/openembedded-core/20260601181251.123019-1-JPEWhacker@gmail.com/
Sounds good! I think Joshua's patches have been merged.
Antonin
prev parent reply other threads:[~2026-06-05 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 10:09 [PATCH] recipe-style-guide: Clarify when License-Update tag is needed Paul Barker
2026-06-04 10:14 ` [docs] " Antonin Godard
2026-06-04 10:18 ` Paul Barker
2026-06-05 14:05 ` Antonin Godard [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=DJ168NAEZ2ZU.ZCFOL92MHAE0@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=paul@pbarker.dev \
/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