Re: [PULL v2 00/73] tcg plugins and testing updates

2019-11-08 Thread Peter Maydell
On Wed, 6 Nov 2019 at 12:42, Markus Armbruster wrote: > > Markus Armbruster writes: > > > Alex Bennée writes: > > > >> Markus Armbruster writes: > >> > >>> I hate to interfere with the merging of working code for non-technical > >>> reasons > >>> > >>> This is a plugin interface. As I wrot

Re: [PULL v2 00/73] tcg plugins and testing updates

2019-11-06 Thread Markus Armbruster
Markus Armbruster writes: > Alex Bennée writes: > >> Markus Armbruster writes: >> >>> I hate to interfere with the merging of working code for non-technical >>> reasons >>> >>> This is a plugin interface. As I wrote in reply to v4, I'd like to see >>> a pragmatic argument why abuse of the

Re: [PULL v2 00/73] tcg plugins and testing updates

2019-10-28 Thread Alex Bennée
Peter Maydell writes: > On Fri, 25 Oct 2019 at 21:24, Markus Armbruster wrote: >> Alex Bennée writes: >> > I'd rather not unless we can make an exception for late merging of the >> > PR. I've worked quite hard to make sure everything is ready for the 4.2 >> > window and I'd rather not miss a

Re: [PULL v2 00/73] tcg plugins and testing updates

2019-10-27 Thread Peter Maydell
On Fri, 25 Oct 2019 at 21:24, Markus Armbruster wrote: > Alex Bennée writes: > > I'd rather not unless we can make an exception for late merging of the > > PR. I've worked quite hard to make sure everything is ready for the 4.2 > > window and I'd rather not miss a whole release cycle on a > > mis

Re: [PULL v2 00/73] tcg plugins and testing updates

2019-10-25 Thread Markus Armbruster
Alex Bennée writes: > Markus Armbruster writes: > >> I hate to interfere with the merging of working code for non-technical >> reasons >> >> This is a plugin interface. As I wrote in reply to v4, I'd like to see >> a pragmatic argument why abuse of the plugin interface to circumvent the >>

Re: [PULL v2 00/73] tcg plugins and testing updates

2019-10-25 Thread Alex Bennée
Peter Maydell writes: > On Fri, 25 Oct 2019 at 07:37, Alex Bennée wrote: >> >> The following changes since commit 81c1f71eeb874c4cbbb9c5c4d1a1dc0ba7391dff: >> >> Merge remote-tracking branch >> 'remotes/ehabkost/tags/machine-next-pull-request' into staging (2019-10-24 >> 10:43:20 +0100) >>

Re: [PULL v2 00/73] tcg plugins and testing updates

2019-10-25 Thread Peter Maydell
On Fri, 25 Oct 2019 at 07:37, Alex Bennée wrote: > > The following changes since commit 81c1f71eeb874c4cbbb9c5c4d1a1dc0ba7391dff: > > Merge remote-tracking branch > 'remotes/ehabkost/tags/machine-next-pull-request' into staging (2019-10-24 > 10:43:20 +0100) > > are available in the Git reposit

Re: [PULL v2 00/73] tcg plugins and testing updates

2019-10-25 Thread Alex Bennée
Markus Armbruster writes: > I hate to interfere with the merging of working code for non-technical > reasons > > This is a plugin interface. As I wrote in reply to v4, I'd like to see > a pragmatic argument why abuse of the plugin interface to circumvent the > GPL is not practical. This m

Re: [PULL v2 00/73] tcg plugins and testing updates

2019-10-25 Thread Markus Armbruster
I hate to interfere with the merging of working code for non-technical reasons This is a plugin interface. As I wrote in reply to v4, I'd like to see a pragmatic argument why abuse of the plugin interface to circumvent the GPL is not practical. This might include "not a stable interface", "y

[PULL v2 00/73] tcg plugins and testing updates

2019-10-24 Thread Alex Bennée
The following changes since commit 81c1f71eeb874c4cbbb9c5c4d1a1dc0ba7391dff: Merge remote-tracking branch 'remotes/ehabkost/tags/machine-next-pull-request' into staging (2019-10-24 10:43:20 +0100) are available in the Git repository at: https://github.com/stsquad/qemu.git tags/pull-testing