All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: which Dom0 should I use in my regular testing?
Date: Tue, 29 May 2012 11:48:10 -0400	[thread overview]
Message-ID: <20120529154810.GA21039@phenom.dumpdata.com> (raw)
In-Reply-To: <1B4B44D9196EFF41AE41FDA404FC0A100D62CB@SHSMSX101.ccr.corp.intel.com>

On Mon, May 28, 2012 at 08:04:40AM +0000, Ren, Yongjie wrote:
> Hi Jackson,
> Our team spares some effort in regular testing against xen-unstable tree.
> I know you are doing some testing against xen.

I am testing against Xen 4.1 and everynight latest Linus's tree.

> Which Dom0 are you using in your oss test, Konrad's xen.git or upstream linux.git ?

I am using Linus' tree everynight. And then whenever I've new patches
I use my #testing or just do

git checkout linus/master
git merge stable/XXX
and test that out.

> And which Dom0 do you recommend in my regular testing?

Uhhh? You mean distro?

> (Not sure you are the right person for this question? :-) )
> 
> Best Regards,
>      Yongjie (Jay)
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2012-05-29 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-28  8:04 which Dom0 should I use in my regular testing? Ren, Yongjie
2012-05-29 14:33 ` Ren, Yongjie
2012-05-29 14:38   ` Ian Campbell
2012-05-29 14:42     ` Pasi Kärkkäinen
2012-05-29 14:50       ` Ian Campbell
2012-05-29 15:29         ` Ren, Yongjie
2012-05-29 15:48 ` Konrad Rzeszutek Wilk [this message]
2012-05-30  1:50   ` Ren, Yongjie

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=20120529154810.GA21039@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yongjie.ren@intel.com \
    /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.