All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Xen 4.2 TODO / Release Plan
Date: Wed, 20 Jun 2012 16:50:07 +0100	[thread overview]
Message-ID: <1340207407.4906.77.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <4FE20B23020000780008AE16@nat28.tlf.novell.com>

On Wed, 2012-06-20 at 16:40 +0100, Jan Beulich wrote:
> > That thread also references
> > <4FABFCF40200007800082CE0@nat28.tlf.novell.com> as something which
> > should be applied to the trad tree too. Has anyone tested that combo?
> > 
> > I can see how Ian missed this -- it very much looked like those two
> > patches were for qemu-upstream only to me (from the subject, cc line etc
> > etc).
> 
> I didn't think that I needed to formally submit patches that were
> requested to be ported over to -traditional when they already
> went into upstream qemu. If I'm wrong with this, then please let
> me know and I'll submit both patches asap.

This is really for Ian J to say but IMHO the two code bases have
diverged enough that blindly pulling from upstream -> traditional is not
a good idea, so at the least the change needs to be tested in that
context.

Even if we were happy to just pull things in then the mail needs to note
somewhere which tree(s) the patch should be applied to. 

Ian.

  parent reply	other threads:[~2012-06-20 15:50 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 13:00 Xen 4.2 TODO / Release Plan Ian Campbell
2012-06-12 13:57 ` Jan Beulich
2012-06-12 14:05   ` Ian Campbell
2012-06-13 10:48     ` Stefano Stabellini
2012-06-20 15:25       ` Ian Campbell
2012-06-20 15:40         ` Jan Beulich
2012-06-20 15:47           ` Ian Jackson
2012-06-20 16:06             ` Jan Beulich
2012-06-20 15:50           ` Ian Campbell [this message]
2012-06-20 15:58             ` Ian Jackson
2012-06-20 15:46         ` Ian Jackson
2012-06-18  8:36 ` Roger Pau Monne
2012-06-18 12:19 ` Dario Faggioli
  -- strict thread matches above, loose matches on Subject: below --
2012-08-28 10:06 Ian Campbell
2012-08-31 17:26 ` George Dunlap
2012-09-03  9:10   ` Ian Campbell
2012-08-31 17:36 ` George Dunlap
     [not found] ` <CAFLBxZaDmZ8bTQzZ_CpQpTros9WFK7Q96v-1Y3zXXWLdciMXTw@mail.gmail.com>
2012-08-31 17:42   ` Konrad Rzeszutek Wilk
2012-09-02  4:46 ` Pasi Kärkkäinen
2012-09-03  9:09   ` Ian Campbell
2012-08-20  9:17 Ian Campbell
2012-08-20 11:06 ` Jan Beulich
2012-08-21 15:14 ` Ren, Yongjie
2012-08-21 15:27   ` Ian Campbell
2012-08-21 15:49     ` Ren, Yongjie
2012-08-21 15:39 ` Ben Guthro
2012-08-21 16:08   ` Jan Beulich
2012-08-14  9:05 Ian Campbell
2012-08-14  9:52 ` Jan Beulich
2012-08-15 15:46 ` George Dunlap
2012-07-30  8:30 Ian Campbell
2012-08-03 10:09 ` Ian Campbell
2012-08-03 10:28   ` Keir Fraser
2012-08-03 10:30     ` Ian Campbell
2012-08-03 10:44     ` Jan Beulich
2012-08-06 17:06       ` Liu, Jinsong
2012-08-07  6:38         ` Jan Beulich
2012-08-07  7:50           ` Keir Fraser
2012-08-07  8:05             ` Jan Beulich
2012-08-07  8:10               ` Ian Campbell
2012-08-07 18:13               ` Liu, Jinsong
2012-08-08  6:37                 ` Jan Beulich
2012-07-17 16:47 Ian Campbell
2012-07-17 16:51 ` Andrew Cooper
2012-05-21 11:47 Ian Campbell
2012-05-21 13:00 ` Pasi Kärkkäinen
2012-05-21 13:05   ` Ian Campbell
2012-05-21 13:32 ` Jan Beulich
2012-05-14 10:26 Ian Campbell
2012-05-14 11:14 ` Jan Beulich
2012-05-29  9:32   ` Ian Campbell
2012-05-29 10:10     ` Jan Beulich
2012-05-31  9:24       ` Olaf Hering
2012-05-31  9:37         ` Jan Beulich
2012-05-31  9:56           ` Stefano Stabellini
2012-05-31 21:43         ` Olaf Hering
2012-05-14 13:51 ` Dario Faggioli
2012-05-14 15:33 ` Ian Jackson
2012-05-14 15:43   ` Ian Campbell
2012-05-14 17:07   ` Dario Faggioli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1340207407.4906.77.camel@zakaz.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.