openembedded-architecture  

Messages by Thread

• [Openembedded-architecture] CVE program statement on the use of the new data format Marta Rybczynska
  • Re: [Openembedded-architecture] CVE program statement on the use of the new data format Richard Purdie
• [Openembedded-architecture] Cleanup of WORKDIR by separating do_unpack Richard Purdie
  • Re: [Openembedded-architecture] Cleanup of WORKDIR by separating do_unpack Mark Hatle
  • Re: [Openembedded-architecture] Cleanup of WORKDIR by separating do_unpack Paul Barker
  • Re: [Openembedded-architecture] Cleanup of WORKDIR by separating do_unpack Richard Purdie
  • Re: [Openembedded-architecture] Cleanup of WORKDIR by separating do_unpack Esben Haabendal
  • Re: [Openembedded-architecture] Cleanup of WORKDIR by separating do_unpack Richard Purdie
  • Re: [Openembedded-architecture] Cleanup of WORKDIR by separating do_unpack Richard Purdie
• [Openembedded-architecture] Security tooling update: VEX, cve-check over SPDX and a plan "B" for the NVD situation Marta Rybczynska
• [Openembedded-architecture] Open letter to the CVE Project/CNAs Richard Purdie
• [Openembedded-architecture] NVD status and ideas for a backup solution Marta Rybczynska
  • Re: [Openembedded-architecture] NVD status and ideas for a backup solution Marta Rybczynska
• [Openembedded-architecture] New mailing list for layer patches Ross Burton
  • Re: [Openembedded-architecture] New mailing list for layer patches Paul Barker
  • Re: [yocto] [Openembedded-architecture] New mailing list for layer patches Michael Opdenacker via lists.openembedded.org
  • Re: [yocto] [Openembedded-architecture] New mailing list for layer patches Josef Holzmayr
  • Re: [Openembedded-architecture] New mailing list for layer patches Peter Kjellerstedt
  • Re: [Openembedded-architecture] New mailing list for layer patches Richard Purdie
  • Re: [Openembedded-architecture] [yocto] New mailing list for layer patches Neal Caidin
• [Openembedded-architecture] Feature freeze status Richard Purdie
  • Re: [Openembedded-architecture] Feature freeze status Alexander Kanavin
  • Re: [Openembedded-architecture] Feature freeze status Richard Purdie
• [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig Ross Burton
  • Re: [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig Richard Purdie
  • Re: [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig Mikko Rapeli
  • Re: [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig Mikko Rapeli
  • Re: [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig Bruce Ashfield
  • Re: [OE-core] [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig Bruce Ashfield
  • Re: [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig Paul Barker
  • Re: [poky] [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig Mark Hatle
  • Re: [Openembedded-architecture] [RFC PATCH] Add genericarm64 MACHINE using upstream defconfig paulg
• [Openembedded-architecture] proposal: config fragments Alexander Kanavin
  • Re: [Openembedded-architecture] proposal: config fragments Richard Purdie
  • Re: [Openembedded-architecture] proposal: config fragments Mark Hatle
  • Re: [Openembedded-architecture] proposal: config fragments Mark Asselstine via lists.openembedded.org
  • Re: [Openembedded-architecture] proposal: config fragments Alexander Kanavin
  • Re: [Openembedded-architecture] proposal: config fragments Bruce Ashfield
• Re: [Openembedded-architecture] Priority removal discussion Josef Holzmayr
• [Openembedded-architecture] Kernel versions in our next LTS release Richard Purdie
• [Openembedded-architecture] Proposal for adding a "inherit_deferred" directive to bitbake Richard Purdie
  • Re: [Openembedded-architecture] Proposal for adding a "inherit_deferred" directive to bitbake Richard Purdie
  • Re: [Openembedded-architecture] Proposal for adding a "inherit_deferred" directive to bitbake Bruce Ashfield
  • Re: [Openembedded-architecture] Proposal for adding a "inherit_deferred" directive to bitbake Chris Laplante via lists.openembedded.org
  • Re: [Openembedded-architecture] Proposal for adding a "inherit_deferred" directive to bitbake Richard Purdie
• [Openembedded-architecture] Removal/disable of testimage dumper code in LTS branches? Richard Purdie
  • Re: [Openembedded-architecture] Removal/disable of testimage dumper code in LTS branches? Khem Raj
  • Re: [Openembedded-architecture] Removal/disable of testimage dumper code in LTS branches? Ross Burton
  • Re: [Openembedded-architecture] Removal/disable of testimage dumper code in LTS branches? Steve Sakoman
  • Re: [Openembedded-architecture] Removal/disable of testimage dumper code in LTS branches? Khem Raj
• [Openembedded-architecture] Weak PACKAGECONFIG removal Joshua Watt
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Alex Kiernan
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Christopher Larson
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Alexander Kanavin
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Richard Purdie
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Richard Purdie
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Joshua Watt
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Peter Kjellerstedt
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Alexander Kanavin
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Ross Burton
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Chen Qi via lists.openembedded.org
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Ross Burton
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Adrian Freihofer
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Joshua Watt
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Peter Kjellerstedt
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Adrian Freihofer
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Alexander Kanavin
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Alex Kiernan
  • Re: [Openembedded-architecture] Weak PACKAGECONFIG removal Richard Purdie
• [Openembedded-architecture] OpenEmbedded Working Group Definition Joshua Watt
• [Openembedded-architecture] Removing moving "early boot" binaries to /bin Ross Burton
  • Re: [Openembedded-architecture] Removing moving "early boot" binaries to /bin Joshua Watt
  • Re: [Openembedded-architecture] Removing moving "early boot" binaries to /bin Richard Purdie
  • Re: [Openembedded-architecture] Removing moving "early boot" binaries to /bin Joshua Watt
• [Openembedded-architecture] Why are sstate task interdependencies a bad idea? Richard Purdie
• [Openembedded-architecture] Should we continue with rpm in oe-core? (dependency explosion: needs rust, clang) Alexander Kanavin
  • Re: [Openembedded-architecture] Should we continue with rpm in oe-core? (dependency explosion: needs rust, clang) Mark Hatle
  • Re: [Openembedded-architecture] Should we continue with rpm in oe-core? (dependency explosion: needs rust, clang) Alexander Kanavin
  • Re: [Openembedded-architecture] Should we continue with rpm in oe-core? (dependency explosion: needs rust, clang) Alex Kiernan
  • Re: [Openembedded-architecture] Should we continue with rpm in oe-core? (dependency explosion: needs rust, clang) Alexander Kanavin
  • Re: [Openembedded-architecture] Should we continue with rpm in oe-core? (dependency explosion: needs rust, clang) Sudip Mukherjee
  • Re: [Openembedded-architecture] Should we continue with rpm in oe-core? (dependency explosion: needs rust, clang) Sudip Mukherjee
  • Re: [Openembedded-architecture] Should we continue with rpm in oe-core? (dependency explosion: needs rust, clang) Alexander Kanavin
• [Openembedded-architecture] Scope of a Yocto binary distribution prototype Michael Opdenacker via lists.openembedded.org
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Mark Hatle
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Alexander Kanavin
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Bruce Ashfield
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Michael Opdenacker via lists.openembedded.org
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Alexander Kanavin
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Bruce Ashfield
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Michael Opdenacker via lists.openembedded.org
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Mark Hatle
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Michael Opdenacker via lists.openembedded.org
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Mark Hatle
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Michael Opdenacker via lists.openembedded.org
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Michael Opdenacker via lists.openembedded.org
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Joshua Watt
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Mark Hatle
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Joshua Watt
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Khem Raj
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Michael Opdenacker via lists.openembedded.org
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Joshua Watt
  • Re: [Openembedded-architecture] Scope of a Yocto binary distribution prototype Mark Hatle
• [Openembedded-architecture] [RFC] Support for alternative init systems ANQUETIN Mathieu
  • Re: [Openembedded-architecture] [RFC] Support for alternative init systems Alexander Kanavin
  • Re: [Openembedded-architecture] [oe] [RFC] Support for alternative init systems Richard Purdie
  • Re: [Openembedded-architecture] [oe] [RFC] Support for alternative init systems Martin Jansa
  • Re: [Openembedded-architecture] [oe] [RFC] Support for alternative init systems Mathieu Anquetin
  • Re: [Openembedded-architecture] [oe] [RFC] Support for alternative init systems Richard Purdie
  • Re: [Openembedded-architecture] [RFC] Support for alternative init systems Ross Burton
  • Re: [Openembedded-architecture] [RFC] Support for alternative init systems Mathieu Anquetin
  • Re: [Openembedded-architecture] [RFC] Support for alternative init systems Alex Kiernan
  • Re: [Openembedded-architecture] [RFC] Support for alternative init systems Martin Jansa
  • Re: [Openembedded-architecture] [RFC] Support for alternative init systems Alex Kiernan
  • Re: [Openembedded-architecture] [RFC] Support for alternative init systems Mathieu Anquetin
• [Openembedded-architecture] Question: supported layers for security processes Marta Rybczynska
  • Re: [Openembedded-architecture] Question: supported layers for security processes Richard Purdie
  • Re: [Openembedded-architecture] [yocto-security] Question: supported layers for security processes Armin Kuster
  • Re: [Openembedded-architecture] [yocto-security] Question: supported layers for security processes Ross Burton
  • Re: [Openembedded-architecture] [yocto-security] Question: supported layers for security processes Richard Purdie
  • Re: [Openembedded-architecture] [yocto-security] Question: supported layers for security processes Marta Rybczynska
  • Re: [Openembedded-architecture] Question: supported layers for security processes Alex Stewart
  • Re: [Openembedded-architecture] Question: supported layers for security processes Richard Purdie
  • Re: [Openembedded-architecture] Question: supported layers for security processes Marta Rybczynska
  • Re: [yocto-security] [Openembedded-architecture] Adding SECURITY.md (Was: Question: supported layers for security processes) Marta Rybczynska
  • Re: [yocto-security] [Openembedded-architecture] Adding SECURITY.md (Was: Question: supported layers for security processes) Alex Stewart
  • Re: [yocto-security] [Openembedded-architecture] Adding SECURITY.md (Was: Question: supported layers for security processes) Bruce Ashfield
  • Re: [Openembedded-architecture] [yocto-security] Question: supported layers for security processes Ross Burton
• [Openembedded-architecture] OE recipe deprecation policy proposal Khem Raj
  • Re: [Openembedded-architecture] OE recipe deprecation policy proposal Mark Hatle
  • Re: [Openembedded-architecture] OE recipe deprecation policy proposal Martin Jansa
  • Re: [Openembedded-architecture] OE recipe deprecation policy proposal Tim Orling
  • Re: [Openembedded-architecture] OE recipe deprecation policy proposal Khem Raj
  • Re: [Openembedded-architecture] OE recipe deprecation policy proposal Armin Kuster
  • Re: [Openembedded-architecture] OE recipe deprecation policy proposal Mark Hatle
• [Openembedded-architecture] YP Security team document Marta Rybczynska
  • Re: [Openembedded-architecture] YP Security team document Richard Purdie
  • Re: [Openembedded-architecture] YP Security team document Ross Burton
  • Re: [yocto-security] [Openembedded-architecture] YP Security team document Marta Rybczynska
• [Openembedded-architecture] Proposal: Patch review meetings Ross Burton
• [Openembedded-architecture] Yocto Project security work in progress: call for contributions Marta Rybczynska
• [Openembedded-architecture] Bitbake server file coherency problems Richard Purdie
• Re: [Openembedded-architecture] [bitbake-devel] [PATCH] server/process: Disable the flush() call in server logging Richard Purdie
  • Re: [Openembedded-architecture] [bitbake-devel] [PATCH] server/process: Disable the flush() call in server logging Peter Kjellerstedt
  • Re: [Openembedded-architecture] [bitbake-devel] [PATCH] server/process: Disable the flush() call in server logging Richard Purdie
  • Re: [Openembedded-architecture] [bitbake-devel] [PATCH] server/process: Disable the flush() call in server logging Richard Purdie
  • Re: [Openembedded-architecture] [bitbake-devel] [PATCH] server/process: Disable the flush() call in server logging Richard Purdie
  • Re: [Openembedded-architecture] [bitbake-devel] [PATCH] server/process: Disable the flush() call in server logging Richard Purdie
  • Re: [Openembedded-architecture] [bitbake-devel] [PATCH] server/process: Disable the flush() call in server logging Richard Purdie
• [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Richard Purdie
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Richard Purdie
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Julien Stephan
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Julien Stephan
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Chris Laplante via lists.openembedded.org
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Richard Purdie
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Richard Purdie
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Richard Purdie
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Adrian Freihofer
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Adrian Freihofer
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Adrian Freihofer
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Richard Purdie
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Adrian Freihofer
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Mark Hatle
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Adrian Freihofer
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Mark Hatle
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Adrian Freihofer
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Richard Purdie
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Richard Purdie
  • Re: [Openembedded-architecture] [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] [yocto] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Adrian Freihofer
  • Re: [Openembedded-architecture] [yocto] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] [yocto] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Adrian Freihofer
  • Re: [Openembedded-architecture] [yocto] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] [yocto] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
  • Re: [Openembedded-architecture] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused? Alexander Kanavin
• [Openembedded-architecture] Security processes: YP needs Marta Rybczynska
  • Re: [Openembedded-architecture] Security processes: YP needs Mikko Rapeli
  • Re: [Openembedded-architecture] Security processes: YP needs Marta Rybczynska
  • Re: [Openembedded-architecture] Security processes: YP needs Mikko Rapeli
  • Re: [Openembedded-architecture] Security processes: YP needs Alex Stewart
  • Re: [Openembedded-architecture] Security processes: YP needs Marta Rybczynska
  • Re: [Openembedded-architecture] [yocto] Security processes: YP needs Reyna, David via lists.openembedded.org
  • Re: [Openembedded-architecture] [yocto] Security processes: YP needs Marta Rybczynska
  • Re: [Openembedded-architecture] [yocto] Security processes: YP needs Reyna, David via lists.openembedded.org
  • Re: [Openembedded-architecture] [yocto] Security processes: YP needs Marta Rybczynska

• Earlier messages