Re: [Qemu-devel] The development tree is now open!
On 06/05/2012 04:19 PM, Jan Kiszka wrote: Note, I am holding off on the qemu-kvm-1.1 release pending investigation of the qcow2/ide bug that Yongjie Ren discovered. But if it's holding you off, I can branch 1.1 now and merge this early to master. I'm optimistic that the pull I sent yesterday should still merge cleanly into a master that contains some qcow2 or whatever fix. That wasn't the issue, rather if we branch now I have to work the fix into both trees. But I'll stop being lazy and pull. -- error compiling committee.c: too many arguments to function
Re: [Qemu-devel] The development tree is now open!
On 06/03/2012 08:05 PM, Jan Kiszka wrote: On 2012-06-02 11:53, Anthony Liguori wrote: Let your PATCHes, PULLs, RFCs, and RFTs start flowing. I'll start applying pull requests on Monday or perhaps earlier if I can find the time. For submaintainers, if you have a very large queue ( 50 patches), please split your pulls into multiple pull requests of reasonable size (~50) and submit them spaced out a week at a time. If you have a lot of safe/trivial patches, of course use your best judgement. Would be great if [1] could be merged quickly as quite some work on qemu-kvm depends on its back-merge. Hopefully, we will be able to finally close the feature gap between qemu-kvm and upstream with 1.2. Note, I am holding off on the qemu-kvm-1.1 release pending investigation of the qcow2/ide bug that Yongjie Ren discovered. But if it's holding you off, I can branch 1.1 now and merge this early to master. -- error compiling committee.c: too many arguments to function
Re: [Qemu-devel] The development tree is now open!
On 2012-06-05 15:07, Avi Kivity wrote: On 06/03/2012 08:05 PM, Jan Kiszka wrote: On 2012-06-02 11:53, Anthony Liguori wrote: Let your PATCHes, PULLs, RFCs, and RFTs start flowing. I'll start applying pull requests on Monday or perhaps earlier if I can find the time. For submaintainers, if you have a very large queue ( 50 patches), please split your pulls into multiple pull requests of reasonable size (~50) and submit them spaced out a week at a time. If you have a lot of safe/trivial patches, of course use your best judgement. Would be great if [1] could be merged quickly as quite some work on qemu-kvm depends on its back-merge. Hopefully, we will be able to finally close the feature gap between qemu-kvm and upstream with 1.2. Note, I am holding off on the qemu-kvm-1.1 release pending investigation of the qcow2/ide bug that Yongjie Ren discovered. But if it's holding you off, I can branch 1.1 now and merge this early to master. I'm optimistic that the pull I sent yesterday should still merge cleanly into a master that contains some qcow2 or whatever fix. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux
Re: [Qemu-devel] The development tree is now open!
On 2012-06-02 11:53, Anthony Liguori wrote: Let your PATCHes, PULLs, RFCs, and RFTs start flowing. I'll start applying pull requests on Monday or perhaps earlier if I can find the time. For submaintainers, if you have a very large queue ( 50 patches), please split your pulls into multiple pull requests of reasonable size (~50) and submit them spaced out a week at a time. If you have a lot of safe/trivial patches, of course use your best judgement. Would be great if [1] could be merged quickly as quite some work on qemu-kvm depends on its back-merge. Hopefully, we will be able to finally close the feature gap between qemu-kvm and upstream with 1.2. Thanks, Jan [1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/91171 signature.asc Description: OpenPGP digital signature
[Qemu-devel] The development tree is now open!
Let your PATCHes, PULLs, RFCs, and RFTs start flowing. I'll start applying pull requests on Monday or perhaps earlier if I can find the time. For submaintainers, if you have a very large queue ( 50 patches), please split your pulls into multiple pull requests of reasonable size (~50) and submit them spaced out a week at a time. If you have a lot of safe/trivial patches, of course use your best judgement. Regards, Anthony Liguori
