From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M6Mxg-0001EX-Sz for qemu-devel@nongnu.org; Tue, 19 May 2009 06:54:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M6Mxc-0001DJ-4J for qemu-devel@nongnu.org; Tue, 19 May 2009 06:54:20 -0400 Received: from [199.232.76.173] (port=40387 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M6Mxc-0001DC-0w for qemu-devel@nongnu.org; Tue, 19 May 2009 06:54:16 -0400 Received: from mail-gx0-f176.google.com ([209.85.217.176]:62195) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M6Mxb-0007Z6-Lq for qemu-devel@nongnu.org; Tue, 19 May 2009 06:54:15 -0400 Received: by gxk24 with SMTP id 24so11831989gxk.10 for ; Tue, 19 May 2009 03:54:14 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <18925.58746.696296.909587@mariner.uk.xensource.com> References: <1240316408-15949-1-git-send-email-kraxel@redhat.com> <18925.58746.696296.909587@mariner.uk.xensource.com> Date: Tue, 19 May 2009 06:54:14 -0400 Message-ID: <521a4d120905190354i7d1c190bwa4a495a33f265e5b@mail.gmail.com> From: Mark Johnson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Re: [Xen-devel] [PATCH 00/10] xen: pv domain support. List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ian Jackson Cc: xen-devel@lists.xensource.com, Gerd Hoffmann , qemu-devel@nongnu.org Hi Ian, On Tue, Apr 21, 2009 at 11:25 AM, Ian Jackson w= rote: > Gerd Hoffmann writes ("[Xen-devel] [PATCH 00/10] xen: pv domain support."= ): >> Next round, addressing review comments: > ... >> Ian, is just pulling from git fine with you? =A0Or do you want the >> qemu-xen patches mailed to xen-devel? > > I think that for form's sake it would be good for you to mail the > patches to xen-devel but I'm happy to pull. =A0So ideally a patch series > submission which says `here are the diffs 0/n and also a git URL'. > Is that a lot of work for you ? =A0If so I can probably produce such a > series of emails myself but I think since you're the originator of > these patches I think it would make more sense for you to do it. > > Thanks for your contributions. =A0I'm definitely keen to have them and > I'll be branching qemu-xen so that I can take your changes now rather > than waiting for the Xen 3.4 release freeze to end. Do you have an idea when you expect to push these to qemu-unstable? Thanks, MRJ > It's good that you're posting this code to qemu-devel and getting > review there. =A0But I'd like the qemu developers to hold off committing > these changes to their tree until the files which are being added are > 100% identical in Gerd's patch series to in qemu-xen-unstable. > > That way qemu upstream will remain directly mergeable into > qemu-xen-unstable because the code in the new files will be identical. > Anything else will make my life very painful. > > To make this happen I'm of course happy to take patches to make sure > that the code which is in qemu-xen-unstable is in the form that qemu > upstream want it for merging. > > Ian. > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >