From: Olaf Hering <olaf@aepfle.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
<xen-devel@lists.xenproject.org>,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [XEN PATCH 2/2] automation: Check if ninja is available before building QEMU
Date: Thu, 8 Jul 2021 14:23:09 +0200 [thread overview]
Message-ID: <20210708142309.6d093d7e.olaf@aepfle.de> (raw)
In-Reply-To: <20210708023224.6c05ff5b.olaf@aepfle.de>
[-- Attachment #1: Type: text/plain, Size: 354 bytes --]
Am Thu, 8 Jul 2021 02:32:24 +0200
schrieb Olaf Hering <olaf@aepfle.de>:
> At least for Tumbleweed it is useful information.
CPE_NAME="cpe:/o:opensuse:tumbleweed:20190730"
Two years old for a rolling release.
Is there any documentation how to refresh the used containers? I think for Tumbleweed this should be done every other week.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-07-08 12:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 16:39 [XEN PATCH 0/2] automation: Fix build with new qemu-xen version Anthony PERARD
2021-07-07 16:40 ` [XEN PATCH 1/2] automation: Adding ninja-build to some docker images Anthony PERARD
2021-07-07 16:40 ` [XEN PATCH 2/2] automation: Check if ninja is available before building QEMU Anthony PERARD
2021-07-07 17:46 ` Andrew Cooper
2021-07-07 19:52 ` Olaf Hering
2021-07-07 22:44 ` Andrew Cooper
2021-07-08 0:29 ` Olaf Hering
2021-07-07 20:35 ` Olaf Hering
2021-07-07 22:47 ` Andrew Cooper
2021-07-08 0:32 ` Olaf Hering
2021-07-08 12:23 ` Olaf Hering [this message]
2021-07-08 12:51 ` Andrew Cooper
2021-07-08 14:20 ` Olaf Hering
2021-07-08 10:52 ` Anthony PERARD
2021-07-08 11:23 ` Andrew Cooper
2021-07-08 11:30 ` Anthony PERARD
2021-07-07 17:23 ` [XEN PATCH 0/2] automation: Fix build with new qemu-xen version Anthony PERARD
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=20210708142309.6d093d7e.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=cardoe@cardoe.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.