On Mon, 04/28 11:56, Peter Maydell wrote:
> QEMU tends to have rather a lot of half-finished API or coding style
> transitions, as an inevitable consequence of our having such a large
> code base with wildly varying levels of maintainedness. I thought it
> would be useful to at least document them
On Mon, 28 Apr 2014 13:52:48 +0200
Kevin Wolf wrote:
> Am 28.04.2014 um 12:56 hat Peter Maydell geschrieben:
> > QEMU tends to have rather a lot of half-finished API or coding style
> > transitions, as an inevitable consequence of our having such a large
> > code base with wildly varying levels o
On 28 April 2014 14:28, Andreas Färber wrote:
> Am 28.04.2014 12:56, schrieb Peter Maydell:
>> QEMU tends to have rather a lot of half-finished API or coding style
>> transitions, as an inevitable consequence of our having such a large
>> code base with wildly varying levels of maintainedness. I t
Am 28.04.2014 12:56, schrieb Peter Maydell:
> QEMU tends to have rather a lot of half-finished API or coding style
> transitions, as an inevitable consequence of our having such a large
> code base with wildly varying levels of maintainedness. I thought it
> would be useful to at least document the
On Mon, 2014-04-28 at 13:33 +0200, Markus Armbruster wrote:
> Peter Maydell writes:
>
> > QEMU tends to have rather a lot of half-finished API or coding style
> > transitions, as an inevitable consequence of our having such a large
> > code base with wildly varying levels of maintainedness. I tho
Am 28.04.2014 um 12:56 hat Peter Maydell geschrieben:
> QEMU tends to have rather a lot of half-finished API or coding style
> transitions, as an inevitable consequence of our having such a large
> code base with wildly varying levels of maintainedness. I thought it
> would be useful to at least do
Peter Maydell writes:
> QEMU tends to have rather a lot of half-finished API or coding style
> transitions, as an inevitable consequence of our having such a large
> code base with wildly varying levels of maintainedness. I thought it
> would be useful to at least document them on the wiki:
>
> h
QEMU tends to have rather a lot of half-finished API or coding style
transitions, as an inevitable consequence of our having such a large
code base with wildly varying levels of maintainedness. I thought it
would be useful to at least document them on the wiki:
http://wiki.qemu.org/CodeTransitions