From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38838) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZuM4j-0001W4-9t for qemu-devel@nongnu.org; Thu, 05 Nov 2015 10:03:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZuM4g-0002Sa-3o for qemu-devel@nongnu.org; Thu, 05 Nov 2015 10:03:41 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60601) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZuM4f-0002SV-UC for qemu-devel@nongnu.org; Thu, 05 Nov 2015 10:03:38 -0500 References: <1446725610.30393.23.camel@redhat.com> <563B586A.1060908@de.ibm.com> <563B6148.8030602@redhat.com> From: Paolo Bonzini Message-ID: <563B6FC1.6060204@redhat.com> Date: Thu, 5 Nov 2015 16:03:29 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Christian Borntraeger , Gerd Hoffmann , QEMU Developers On 05/11/2015 15:52, Peter Maydell wrote: > ...also speaking as the person who does the wrangling of freezes and > rc candidate tags and so on, three times a year is quite enough :-) That's actually a good reason. On the other hand, we could look for a new policy that makes your work shorter during freezes. We could also find a second committer when you're on vacation, though that would be harder. 4 months (120 days = 17 weeks) does have an advantage, in that it's pretty much synced with the kernel's 9 week cycle if we insert a "leap week" here and there. That theoretically means there's no reason to sync headers from anything other than mainline. Paolo