From: Doug Goldstein <cardoe@cardoe.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "meta-virtualization@yoctoproject.org"
<meta-virtualization@yoctoproject.org>
Subject: Re: jethro branch?
Date: Mon, 1 Feb 2016 10:00:28 -0600 [thread overview]
Message-ID: <56AF811C.6090001@cardoe.com> (raw)
In-Reply-To: <CADkTA4OXKN7hsWxRVHVDWvtxiFDC5vrcksHRJqi7c1y=psw90A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2113 bytes --]
On 1/31/16 11:28 PM, Bruce Ashfield wrote:
>
>
> On Thu, Jan 28, 2016 at 9:35 PM, Doug Goldstein <cardoe@cardoe.com
> <mailto:cardoe@cardoe.com>> wrote:
>
> On 1/28/16 6:25 PM, Bruce Ashfield wrote:
> >
> >
> > On Thu, Jan 28, 2016 at 3:12 PM, Doug Goldstein <cardoe@cardoe.com <mailto:cardoe@cardoe.com>
> > <mailto:cardoe@cardoe.com <mailto:cardoe@cardoe.com>>> wrote:
> >
> > Hi all,
> >
> > With the addition of the linux-yocto_4.4.bbappend, master no longer
> > works with jethro. Could we land the Xen patches I proposed and then
> > create a jethro branch and drop linux-yocto_4.4.bbappend from that
> > branch?
> >
> >
> > I actually have a jethro branch prep'd already. Once I've merged the pending
> > changes to master, I'll cherry pick them to the jethro and push both
> > branches.
> >
> > Bruce
>
> Thanks Bruce.
>
>
> I just pushed a preliminary jethro branch.
>
> oe-core/yocto branched jethro Nov 3rd 2015, and I did the same at the
> time. Looking
> at the newer changes in meta-virt, I updated my jethro branch up to the
> point where
> I cloned the 4.1 xen config to 4.4 .. since that creates a dangling
> bbappend in the
> context of jethro.
>
> At this point, I'd like enlist the help of those that are building xen
> regularly, to
> point out the additional commits that should be merged.
>
> Either a branch for a pull request, or just a list of hashes in master
> will work.
>
> Bruce
Thanks Bruce. The changes that I'm building for jethro are the following:
45de52d11c68cf023566c0d6d4fd341adfb04c7b
ec4b409bd6567e430511e767ac043066ddfc850c
12a7d544f40fb911b706c681b611a7cbdd303c39
a19e5567dc9f34d0c52fdb40544f82bba41bf0d0
5817c4a29b361812b87eddb2bbb623344dccbdc2
663463da0c29e1f22b0740335d193f637174c104
3915d59fdf7af575b7e26a82efb0f998864d8692
f5649753869888606de09701ea9f9a56424cd3d8
You can also pull it from here:
https://github.com/cardoe/meta-virtualization/tree/jethro-updates
--
Doug Goldstein
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 978 bytes --]
next prev parent reply other threads:[~2016-02-01 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 20:12 jethro branch? Doug Goldstein
2016-01-29 0:25 ` Bruce Ashfield
2016-01-29 2:35 ` Doug Goldstein
2016-02-01 5:28 ` Bruce Ashfield
2016-02-01 16:00 ` Doug Goldstein [this message]
2016-02-01 20:34 ` Bruce Ashfield
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=56AF811C.6090001@cardoe.com \
--to=cardoe@cardoe.com \
--cc=bruce.ashfield@gmail.com \
--cc=meta-virtualization@yoctoproject.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.