From: Ian Campbell <Ian.Campbell@XenSource.com>
To: "You, Yongkang" <yongkang.you@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xensource.com>
Subject: RE: Does latest xen-unstable build failed?
Date: Wed, 26 Sep 2007 17:14:58 +0100 [thread overview]
Message-ID: <1190823298.4381.9.camel@localhost.localdomain> (raw)
In-Reply-To: <094BCE01AFBE9646AF220B0B3F367AAB02385C26@pdsmsx413.ccr.corp.intel.com>
On Thu, 2007-09-27 at 00:09 +0800, You, Yongkang wrote:
> Hi Ian,
>
> Thanks for the reply.
> I do manually pull linux-2.6.18-xen.hg tree. But it is already the
> latest one for xen-unstable.
> http://xenbits.xensource.com/linux-2.6.18-xen.hg
>
> hg tip
> changeset: 208:d2bd9af846b5
> tag: tip
> user: Christian Limpach <Christian.Limpach@xensource.com>
> date: Tue Sep 11 16:38:13 2007 +0100
> summary: Add the CDROM_GET_CAPABILITY ioctl to blkfront.
>
> Maybe forget to pull from staging tree?
Yes, it looks like the xen-unstable staging tree has been flowing
through but the linux-2.6.18-xen one hasn't. I think the automated
systems do this right so I suspect that someone manually pushed through
xen-unstable and forgot the Linux tree.
I'd pull from the Linux staging tree for now if I were you, regression
tests should pass quite soon at which point both staging trees should
sync out to the main ones.
Ian.
prev parent reply other threads:[~2007-09-26 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 15:53 Does latest xen-unstable build failed? You, Yongkang
2007-09-26 16:02 ` Ian Campbell
2007-09-26 16:09 ` You, Yongkang
2007-09-26 16:14 ` Ian Campbell [this message]
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=1190823298.4381.9.camel@localhost.localdomain \
--to=ian.campbell@xensource.com \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=yongkang.you@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.