From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Josip Rodin <joy@entuzijast.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen patches are in 2.6.37
Date: Sat, 30 Oct 2010 12:29:00 -0700 [thread overview]
Message-ID: <4CCC71FC.7020801@goop.org> (raw)
In-Reply-To: <20101029181006.GA19688@entuzijast.net>
On 10/29/2010 11:10 AM, Josip Rodin wrote:
> Are you going to make a temporary branch where you'll just slap on the
> missing code (even the non-upstreamable parts), just so we can test the full
> Xen dom0 stack in the current circumstances? Upstream kernel has undergone
> many changes since .32 and it stands to reason that there are other bugs to
> flush out, unrelated to code upstreamability.
Yes, I want to keep a full-featured Xen kernel tracking upstream
releases. But I'd like to put a strong emphasis on making sure that
components which must be upstreamed (ie, to get a useful system), or are
very close to upstreamable should be kept in an upstreamable form.
In general, stuff that I think is plausible for upstream, or actually
being upstreamed, will be in upstream/*. Those branches are also
highly dynamic (rebasing, etc), so never use them as the base for your
own branches...
J
next prev parent reply other threads:[~2010-10-30 19:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 7:36 xen patches are in 2.6.37 M A Young
2010-10-29 9:46 ` Pasi Kärkkäinen
2010-10-29 12:12 ` Stefano Stabellini
2010-10-29 14:45 ` Konrad Rzeszutek Wilk
2010-10-29 16:19 ` Bruce Edge
2010-10-29 16:49 ` Jeremy Fitzhardinge
2010-10-29 18:10 ` Josip Rodin
2010-10-30 19:29 ` Jeremy Fitzhardinge [this message]
2010-10-30 16:04 ` Thomas Goirand
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=4CCC71FC.7020801@goop.org \
--to=jeremy@goop.org \
--cc=joy@entuzijast.net \
--cc=xen-devel@lists.xensource.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.