From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] QEMU 2.9.0-rc1
Date: Thu, 30 Mar 2017 19:37:10 -0400 [thread overview]
Message-ID: <20170330233710.GA12960@jasmine> (raw)
In-Reply-To: <87bmsifttx.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
On Thu, Mar 30, 2017 at 09:27:54PM +0200, Marius Bakke wrote:
> Leo Famulari <leo@famulari.name> writes:
> > gnu: qemu: Update to 2.9.0-rc1 [security fixes].
>
> I think it would be nice to have this in Guix proper (as a separate
> variable), so users don't have to apply this patch and build it
> manually. The downside is that it would land in users' profiles unless
> they take steps to prevent it, but I'm not sure how much of a problem
> that is given how easy it is to roll-back or exclude it. Thoughts?
I'm unsure if we should add it. QEMU usually goes through 4 or 5 release
candidates.
Does anyone have experience using these heavily? Are they stable or can
we expect them to be buggier than a real release?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-30 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 8:06 [PATCH 0/1] QEMU 2.9.0-rc1 Leo Famulari
2017-03-28 8:06 ` [PATCH 1/1] gnu: qemu: Update to 2.9.0-rc1 [security fixes] Leo Famulari
2017-04-07 13:12 ` Leo Famulari
2017-03-30 19:27 ` [PATCH 0/1] QEMU 2.9.0-rc1 Marius Bakke
2017-03-30 23:37 ` Leo Famulari [this message]
2017-03-31 8:03 ` Ludovic Courtès
2017-04-01 0:01 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170330233710.GA12960@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).