From: Ian Campbell <Ian.Campbell@citrix.com>
To: Thomas Leonard <talex5@gmail.com>
Cc: xen-devel@lists.xenproject.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Xen 4.5 development update (October update). RC1 on 24th
Date: Mon, 20 Oct 2014 10:34:09 +0100 [thread overview]
Message-ID: <1413797649.12595.15.camel@citrix.com> (raw)
In-Reply-To: <CAG4opy8OEijEwZS6GDjeRKJ_XL-fVDW_Q+dDoPiCq00rVWdX0w@mail.gmail.com>
(trimming CC)
> > == Completed ==
>
> > * ARM - MiniOS (done)
> > v7 posted
> > - Thomas Leonard
>
> This is not done (not all patches were applied). I posted v8 on 3 Oct
> (no responses yet):
>
> http://lists.xenproject.org/archives/html/xen-devel/2014-10/msg00395.html
Oh, somehow I missed this (I had it in my mind you were on vac I think).
WRT the freeze my thinking is that this isn't yet tied into the toplevel
build so baring any interactions with either the common or x86 specific
mini-os code there would be no downside to committing this even fairly
late in the release cycle. I think whatever happens it would be
considered at best "experimental" for 4.5.
Ian.
next prev parent reply other threads:[~2014-10-20 9:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 17:14 Xen 4.5 development update (October update). RC1 on 24th konrad.wilk
2014-10-17 18:44 ` Wei Liu
2014-10-17 18:45 ` Thomas Leonard
2014-10-20 9:34 ` Ian Campbell [this message]
2014-10-20 21:35 ` Konrad Rzeszutek Wilk
2014-10-21 10:27 ` Ian Campbell
2014-10-21 10:35 ` Thomas Leonard
2014-10-17 21:40 ` Boris Ostrovsky
2014-10-18 8:47 ` Arianna Avanzini
2014-10-20 8:09 ` Olaf Hering
2014-10-20 21:30 ` Konrad Rzeszutek Wilk
2014-10-21 12:24 ` Olaf Hering
2014-10-21 14:36 ` Konrad Rzeszutek Wilk
2014-10-20 9:54 ` Jan Beulich
2014-10-20 21:33 ` Konrad Rzeszutek Wilk
2014-10-21 10:54 ` Tamas K Lengyel
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=1413797649.12595.15.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=talex5@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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.