From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41515) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c6bQH-0004an-Je for qemu-devel@nongnu.org; Tue, 15 Nov 2016 05:57:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c6bQD-0004OS-VM for qemu-devel@nongnu.org; Tue, 15 Nov 2016 05:57:05 -0500 Received: from mail-wm0-x244.google.com ([2a00:1450:400c:c09::244]:35756) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c6bQD-0004O4-O9 for qemu-devel@nongnu.org; Tue, 15 Nov 2016 05:57:01 -0500 Received: by mail-wm0-x244.google.com with SMTP id a20so24555626wme.2 for ; Tue, 15 Nov 2016 02:57:01 -0800 (PST) Date: Tue, 15 Nov 2016 10:56:57 +0000 From: Stefan Hajnoczi Message-ID: <20161115105657.GD4836@stefanha-x1.localdomain> References: <1478887767-31980-1-git-send-email-mst@redhat.com> <20161114155258.GC26664@stefanha-x1.localdomain> <20161115011418-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C1iGAkRnbeBonpVg" Content-Disposition: inline In-Reply-To: <20161115011418-mutt-send-email-mst@kernel.org> Subject: Re: [Qemu-devel] [PULL v2 00/34] virtio, vhost, pc, pci: tests, documentation, fixes and cleanups List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: qemu-devel@nongnu.org, Peter Maydell --C1iGAkRnbeBonpVg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 15, 2016 at 01:19:40AM +0200, Michael S. Tsirkin wrote: > Well I feel bad about it. > It was ready in time, I deferred it because there was so much other > stuff that I did not want it to interfere with. >=20 > I was sure it's ok - it's just a test change, I don't really see why we > need to enforce policy for tests, they are not used in production. >=20 > Let's make an exception for once? I've enforced the freeze policy with other maintainers. It isn't fair to make an exception. Build and test changes may appear innocent but they can break other platforms/compilers. That causes delays in the release process and we're stuck in freeze for even longer. As I mentioned, just put it in your -next tree. Everyone working off this code needs to rebase to -next anyway since we'll be in hard freeze for a few weeks starting tomorrow. I see no justification for including these patches. Stefan --C1iGAkRnbeBonpVg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEbBAEBAgAGBQJYKun5AAoJEJykq7OBq3PIDM8H9i1bjc5T+srDD0gQLIZUYutk 5pwVp+boIVChxBsL/yzFbr6WjWfeFf6362aHNEvXZQfsJM9bQgqJwLtzkLteCDNc m+UM4f+GlhT772ZJnhWt7oDOt9y8IhXNuIAt9sLukqhltpe3LBDTJD8qq1tHMGka e/o5n8ZUU1awKSHEgPJnPoPEpEgQABsRf2Izl3vwbv041lw4RYMlrTg6C4YjXD8f DVqkQHa69y5/k2BpzWfT6ncuSZUE3h42jnHL4JoSehBXDXGrNtPxViZq4wyJcmg2 kmd+/mtbLOuwaw4co36zRTPjRyv7hAAbnalX1PAs/1JChu3wQ8w4aa2jnSKG8Q== =dK2w -----END PGP SIGNATURE----- --C1iGAkRnbeBonpVg--