From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37840) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXuip-0002cR-NM for qemu-devel@nongnu.org; Mon, 22 Feb 2016 12:56:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aXuim-0005QA-Cx for qemu-devel@nongnu.org; Mon, 22 Feb 2016 12:56:35 -0500 Received: from mx1.redhat.com ([209.132.183.28]:37773) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXuim-0005Q4-8X for qemu-devel@nongnu.org; Mon, 22 Feb 2016 12:56:32 -0500 References: From: John Snow Message-ID: <56CB4BCD.3010006@redhat.com> Date: Mon, 22 Feb 2016 12:56:29 -0500 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Incremental backup call List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi , qemu-devel Cc: Kevin Wolf , "Denis V. Lunev" , Vladimir Sementsov-Ogievskiy , Fam Zheng On 02/16/2016 09:02 AM, Stefan Hajnoczi wrote: > Hi, > There are several ongoing efforts to implement incremental > backup-related features. > > Let's have a voice/video conference to get everyone on the same page, > avoid duplicated work, and get patches merged faster. > > Agenda: > > * External incremental backup API. Summarize requirements common to > third-party backup appliances and agree on suitable API direction. > > * Persistent dirty bitmaps. Agree on how qcow2 and/or qbm will hold > bitmaps in various use cases. > > * Anything else? > > Date: Tuesday, 23 February at 13:00 GMT > URL: https://bluejeans.com/298720067 > > If you are on the CC list and the time is inconvenient for you, please > let me know so we can reschedule. The call is public and open to > anyone. > > Stefan > Time works for me if it's suitable for everyone else. --js