From: Anthony Liguori <aliguori@us.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] 1.4 release schedule
Date: Tue, 04 Dec 2012 16:00:37 -0600 [thread overview]
Message-ID: <87d2yp4gvu.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA-1szUyDjjo_vO-Am1jyVagOvWSpoAoyMR8mi11Yo7U=Q@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 4 December 2012 18:38, Blue Swirl <blauwirbel@gmail.com> wrote:
>> The definition of the hard freeze bothers me. A few patches that went
>> in after 1.3-rc0 were not bug fixes but just new features, so the
>> difference between soft and hard freezes was not clear.
>
> My vote for this would be to adhere to our definition
> and only commit bugfixes.
Let's get specific. What was committed post hard freeze that's not a
bug fix?
The only thing I'm aware of is q35. I asked Michael not to merge that
(he planned to) prior to the hard freeze because there was a specific
change I wanted to be made. Normally, PCI bits would go through
Michael's tree but I felt the change really needed to be made.
So I agreed to take the bits post hard freeze so the change could be
made. This is really was an exceptional case though and I don't think
it warrants a change in the description of hard freeze. This was all
discussed on the mailing list too FWIW.
Regards,
Anthony Liguori
>
> -- PMM
next prev parent reply other threads:[~2012-12-05 0:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 21:30 [Qemu-devel] [RFC] 1.4 release schedule Anthony Liguori
2012-12-03 21:34 ` Johnson, Eric
2012-12-03 21:41 ` Anthony Liguori
2012-12-04 18:38 ` Blue Swirl
2012-12-04 18:42 ` Peter Maydell
2012-12-04 19:16 ` Blue Swirl
2012-12-04 22:00 ` Anthony Liguori [this message]
2012-12-05 19:28 ` Blue Swirl
2012-12-05 19:41 ` Hans de Goede
2012-12-05 19:58 ` Blue Swirl
2012-12-06 8:05 ` Markus Armbruster
2012-12-06 21:27 ` Blue Swirl
2012-12-06 10:19 ` Kevin Wolf
2012-12-06 21:45 ` Blue Swirl
2012-12-06 9:01 ` Andreas Färber
2012-12-06 21:35 ` Blue Swirl
2012-12-04 18:41 ` Peter Maydell
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=87d2yp4gvu.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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 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.