From: Peter Maydell <peter.maydell@linaro.org>
To: Greg Kurz <groug@kaod.org>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
qemu-ppc <qemu-ppc@nongnu.org>, "Cédric Le Goater" <clg@kaod.org>,
"Igor Mammedov" <imammedo@redhat.com>,
"Jiri Denemark" <jdenemar@redhat.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] spapr/kvm: Set default cpu model for all machine classes
Date: Wed, 13 Nov 2019 15:31:58 +0000 [thread overview]
Message-ID: <CAFEAcA9+VzDC9N5vGcA9COUaPsSue9VWmtoaPneCqY7drtbVzA@mail.gmail.com> (raw)
In-Reply-To: <20191113160900.5f9f5415@bahia.lan>
On Wed, 13 Nov 2019 at 15:10, Greg Kurz <groug@kaod.org> wrote:
> David is away until the 19th of November, which is the release date
> of rc2 according to the planning [*]. Then we have rc3 the 26th, and
> final release (or rc4) the 3rd of December, so it should be ok.
Please don't actively plan to delay putting changes in
until later release candidates. The release process
involves steadily winding up the bar of whether it's
worth putting in and hopefully reducing the volume
of changes between rcs. In an ideal world rc3 would
have very few changes, and then there would be no
changes at all between rc3 and the final release.
thanks
-- PMM
next prev parent reply other threads:[~2019-11-13 16:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 16:32 [PATCH] spapr/kvm: Set default cpu model for all machine classes David Gibson
2019-10-30 17:32 ` David Hildenbrand
2019-10-31 10:06 ` David Gibson
2019-10-30 18:16 ` no-reply
2019-10-30 19:38 ` no-reply
2019-10-31 8:15 ` Greg Kurz
2019-10-31 10:07 ` David Gibson
2019-10-31 8:28 ` Peter Maydell
2019-10-31 8:34 ` Peter Maydell
2019-11-01 12:27 ` Jiri Denemark
2019-11-13 14:43 ` Jiri Denemark
2019-11-13 15:09 ` Greg Kurz
2019-11-13 15:31 ` Peter Maydell [this message]
2019-11-13 16:00 ` Greg Kurz
2019-11-15 9:20 ` David Gibson
2019-11-15 10:42 ` Laurent Vivier
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=CAFEAcA9+VzDC9N5vGcA9COUaPsSue9VWmtoaPneCqY7drtbVzA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=groug@kaod.org \
--cc=imammedo@redhat.com \
--cc=jdenemar@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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 NNTP newsgroup(s).