From: "Andreas Färber" <afaerber@suse.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC] 1.4 release schedule
Date: Thu, 06 Dec 2012 10:01:30 +0100 [thread overview]
Message-ID: <50C05EEA.3060505@suse.de> (raw)
In-Reply-To: <CAAu8pHtizofSMXpZy0s629OM_qi68t8Y95Yav_Y1jjMrE9_ypA@mail.gmail.com>
Am 05.12.2012 20:28, schrieb Blue Swirl:
> On Tue, Dec 4, 2012 at 10:00 PM, Anthony Liguori <aliguori@us.ibm.com> wrote:
>> What was committed post hard freeze that's not a
>> bug fix?
>
> d3067b0 Documentation: Update image format information
> a13e5e0 Documentation: Update block cache mode information
> 044d003 qemu-tech.texi: update implemented xtensa features list
> a0a7068 target-i386: Enable SSSE3 TCG support
Fixed a regression - cf. commit message
> 80ae416 target-i386/cpu: Add missing flags to Haswell CPU model
Bug fix - keyword "missing", we certainly did not want backwards
compatibility issues for a newly introduced model.
> 42015c9 virtio-rng: fix typos, comments
> e1e54f3 target-i386: cpu: add missing flags to Haswell CPU model
Same as above.
> 339c270 qom: make object_finalize static
Not a bugfix and agreed as not needed for 1.3 but still applied
> 64b625f qdev: simplify (de)allocation of buses
> fde9bf4 qom: make object_delete usable for statically-allocated objects
> 667d22d qdev: move bus removal to object_unparent
Bug fix with preparations
> 74c856e tests: add thread pool unit tests
> b2ea25d tests: add AioContext unit tests
> 21022c9 q35: Add kvmclock support
> a1c9304 ich9: Add i82801b11 dmi-to-pci bridge
> df2d8b3 q35: Introduce q35 pc based chipset emulator
> 678e7b9 ich9: Add smbus
> 4d00636 ich9: Add the lpc chip
> e516572 ich9: Add acpi support and definitions
> 410edd9 pc/piix_pci: factor out smram/pam logic
> d8ee038 pc_piix: Move kvm irq routing functions out of pc_piix.c
> a39e356 pc: Move ioapic_init() from pc_piix.c to pc.c
> 9011a1a pc, pc_piix: split out pc nic initialization
> 723aedd usb-redir: Don't handle interrupt output packets async
> 234e810 usb-redir: Split usb_handle_interrupt_data into separate
> in/out functions
> 33c1a68 usb-bt: Return NAK instead of STALL when interrupt ep has no data
> 1bc6b70 block: add bdrv_reopen() support for raw hdev, floppy, and cdrom
> d132c79 target-mips: Add comments on POOL32Axf encoding
Generally I have been in favor of allowing patches that improve the
quality of the release while not introducing regressions, like typo
fixes or documentation updates. This cycle I was much stricter with the
only-bugfixes rule so I don't understand your complaint.
If for any reason you think a certain PATCH or PULL should not be
applied at a certain point in time, feel free to reply before it gets
committed/merged, which is usually several days later.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-12-06 9:01 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
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 [this message]
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=50C05EEA.3060505@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.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.