On Wed, May 11, 2022 at 03:11:01PM +0100, Daniel P. Berrangé wrote:
> On Wed, May 11, 2022 at 03:07:43PM +0100, Daniel P. Berrangé wrote:
> > On Wed, May 11, 2022 at 04:04:54PM +0200, Erik Skultety wrote:
> > > On Wed, May 11, 2022 at 03:01:51PM +0100, Daniel P. Berrangé wrote:
> > > > On Fri, May
On Wed, May 11, 2022 at 03:07:43PM +0100, Daniel P. Berrangé wrote:
> On Wed, May 11, 2022 at 04:04:54PM +0200, Erik Skultety wrote:
> > On Wed, May 11, 2022 at 03:01:51PM +0100, Daniel P. Berrangé wrote:
> > > On Fri, May 06, 2022 at 05:35:18PM +0200, Erik Skultety wrote:
> > > > Rather than writi
On Wed, May 11, 2022 at 04:04:54PM +0200, Erik Skultety wrote:
> On Wed, May 11, 2022 at 03:01:51PM +0100, Daniel P. Berrangé wrote:
> > On Fri, May 06, 2022 at 05:35:18PM +0200, Erik Skultety wrote:
> > > Rather than writing down the steps to build QEMU from source ourselves
> > > let's recycle wh
On Wed, May 11, 2022 at 03:01:51PM +0100, Daniel P. Berrangé wrote:
> On Fri, May 06, 2022 at 05:35:18PM +0200, Erik Skultety wrote:
> > Rather than writing down the steps to build QEMU from source ourselves
> > let's recycle what upstream QEMU uses in their CI. This has the obvious
> > advantage t
On Fri, May 06, 2022 at 05:35:18PM +0200, Erik Skultety wrote:
> Rather than writing down the steps to build QEMU from source ourselves
> let's recycle what upstream QEMU uses in their CI. This has the obvious
> advantage that if QEMU changes something in their upstream CI build
> process we'll pul
Rather than writing down the steps to build QEMU from source ourselves
let's recycle what upstream QEMU uses in their CI. This has the obvious
advantage that if QEMU changes something in their upstream CI build
process we'll pull the change automatically.
Since YAML anchors cannot be used in a cros
