From: Jose Quaresma <quaresma.jose@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org,
Jose Quaresma <jose.quaresma@foundries.io>
Subject: Re: [bitbake-devel] [PATCH] bitbake.conf remove duplicate PERSISTENT_DIR
Date: Thu, 14 Dec 2023 13:03:05 +0000 [thread overview]
Message-ID: <CANPvuR=yQCznyniv52_HoBOu+NZ==o7qqio4CEscmwgFtPY+_Q@mail.gmail.com> (raw)
In-Reply-To: <08612b947964d6b22c8dbe6d3cc7188a1ae4b01d.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
Richard Purdie <richard.purdie@linuxfoundation.org> escreveu no dia quinta,
14/12/2023 à(s) 12:32:
> On Thu, 2023-12-14 at 09:13 +0000, Jose Quaresma wrote:
> > Hi,
> >
> > This patch was merged in bitbake master:
> >
> > f88f314c toaster: Commandline build import table improvements
> > -> 13cbc987 bitbake.conf remove duplicate PERSISTENT_DIR
> > da7f91d6 bitbake: toaster: add functional testing toaster error
> > details
> >
> > but I can't see it on poky master:
> >
> > 524255ad26 bitbake: toaster: Commandline build import table
> > improvements
> > dc608a5bbe bitbake: bitbake: toaster: add functional testing toaster
> > error details
> > 799c131d92 bitbake: toaster: remove test and update setup to avoid
> > rebuilding image
> >
> > Is there a bug somewhere?
>
> That file doesn't exist in poky since historically, two bitbake.conf
> files was considered confusing.
>
> https://git.yoctoproject.org/poky-config/tree/combo-layer.conf#n8
I didn't know this detail.
Thanks
>
>
> Cheers,
>
> Richard
>
--
Best regards,
José Quaresma
[-- Attachment #2: Type: text/html, Size: 1956 bytes --]
prev parent reply other threads:[~2023-12-14 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17A012684A72999E.8967@lists.openembedded.org>
2023-12-14 9:13 ` [bitbake-devel] [PATCH] bitbake.conf remove duplicate PERSISTENT_DIR Jose Quaresma
2023-12-14 12:32 ` Richard Purdie
2023-12-14 13:03 ` Jose Quaresma [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='CANPvuR=yQCznyniv52_HoBOu+NZ==o7qqio4CEscmwgFtPY+_Q@mail.gmail.com' \
--to=quaresma.jose@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jose.quaresma@foundries.io \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).