From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
M A Young <m.a.young@durham.ac.uk>
Subject: Re: the latest dom0 tree
Date: Thu, 23 Apr 2009 10:22:24 -0700 [thread overview]
Message-ID: <49F0A3D0.9030409@goop.org> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098401D1848634@PDSMSX501.ccr.corp.intel.com>
Jiang, Yunhong wrote:
> Thanks for your information. Seems xen-tip/next is changed in April 14 while push2/xen/dom0/master is still in Mar 29. Can I assume all patch is hackery or push2/xen/dom0/master is in xen-tip/next already? If yes, I will base my patch on xen-tip/next.
Yes, that would work. Though preferably you could base your topic
branch on the most appropriate topic branch and work on that (so that
unrelated upstream changes don't have an impact on your work).
J
next prev parent reply other threads:[~2009-04-23 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 8:53 the latest dom0 tree Jiang, Yunhong
2009-04-20 10:28 ` M A Young
2009-04-20 15:09 ` Jiang, Yunhong
2009-04-20 19:15 ` M A Young
2009-04-23 1:43 ` Jiang, Yunhong
2009-04-23 17:22 ` Jeremy Fitzhardinge [this message]
2009-04-24 1:51 ` Jiang, Yunhong
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=49F0A3D0.9030409@goop.org \
--to=jeremy@goop.org \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@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.