From: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: haicheng.li@intel.com, xen-devel@lists.xensource.com,
Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
Subject: Re: Regressions introduced by ioemu-remote -- Xen #18039.
Date: Mon, 14 Jul 2008 13:51:41 +0100 [thread overview]
Message-ID: <18555.19421.880339.604606@mariner.uk.xensource.com> (raw)
In-Reply-To: <C4A0D34F.23F4B%keir.fraser@eu.citrix.com>
Keir Fraser writes ("Re: [Xen-devel] Regressions introduced by ioemu-remote -- Xen #18039."):
> Actually this is already applied to out private tree but hasn't been
> automatically pushed publicly for some reason. I'm sure Ian will sort it out
> today.
I've been investigating this. A manual push worked, using the same
rune as the automatic system is using. I haven't yet managed to
determine which the automatic patchman-controlled push didn't work.
I've added some more diagnostics and will keep an eye on it.
Ian.
next prev parent reply other threads:[~2008-07-14 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 7:54 Regressions introduced by ioemu-remote -- Xen #18039 Li, Haicheng
2008-07-14 8:38 ` Yosuke Iwamatsu
2008-07-14 8:56 ` Keir Fraser
2008-07-14 12:51 ` Ian Jackson [this message]
2008-07-14 8:58 ` Keir Fraser
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=18555.19421.880339.604606@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=haicheng.li@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=y-iwamatsu@ab.jp.nec.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.