From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "roberto.foglietta@linuxteam.org"
<roberto.foglietta@linuxteam.org>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "roberto.foglietta@gmail.com" <roberto.foglietta@gmail.com>
Subject: Re: [PATCH] RECIPE-API-CHANGELOG.md syntax type for bitbake2
Date: Mon, 13 Feb 2023 02:32:09 +0000 [thread overview]
Message-ID: <9bc3cc1559647be7e495ec9cd58c0d13ab76c8ff.camel@siemens.com> (raw)
In-Reply-To: <20230212225617.501412-1-roberto.foglietta@linuxteam.org>
On Sun, 2023-02-12 at 23:56 +0100, roberto.foglietta@linuxteam.org
wrote:
> From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
>
> RECIPE-API-CHANGELOG.md syntax type for bitbake2
>
> Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> ---
> RECIPE-API-CHANGELOG.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
> index e48c98c..2f3a129 100644
> --- a/RECIPE-API-CHANGELOG.md
> +++ b/RECIPE-API-CHANGELOG.md
> @@ -192,7 +192,7 @@ files and patches using bbappend a lot easier.
>
> For example:
> ```
> -FILESEXTRAPATHS_prepend := "$THISDIR/files:"
> +FILESEXTRAPATHS:prepend := "$THISDIR/files:"
NACK. This changelog entry has been added long before the bitbake 2.0
migration. By that, it should also use the old syntax.
Felix
> ```
>
> ### multiconfig build targets were renamed
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-02-13 2:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 22:56 roberto.foglietta
2023-02-13 2:32 ` Moessbauer, Felix [this message]
2023-02-13 3:49 ` Roberto A. Foglietta
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=9bc3cc1559647be7e495ec9cd58c0d13ab76c8ff.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@gmail.com \
--cc=roberto.foglietta@linuxteam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox