From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Cody P Schafer <dev@codyps.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: bump linux-yocto-dev to 3.18?
Date: Wed, 17 Dec 2014 13:07:55 -0500 [thread overview]
Message-ID: <5491C67B.7030901@windriver.com> (raw)
In-Reply-To: <CAPoQQ-3eq6N6j2R=0b6q0k0DXQqh_vN7EZ6jD_4mxPXU61eNgA@mail.gmail.com>
On 14-12-17 01:02 PM, Cody P Schafer wrote:
> It looks like http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/
> is still sitting at 3.17.6, are their plans to merge the 3.18 changes?
>
> Or does linux-yocto-dev wait on stable kernel releases?
> Or is this blocked on something else I'm unaware of?
I'm actually waiting for 3.19 at this point. If you look at the patch
series I sent out last week, we were busy working on developer
experience patches and integrating LTSI content.
There's also another activity to get linux-yocto-dev glued fully into
the autobuilder to shake out bugs before I push the changes to the
the main repositories.
Generally speaking, I don't merge each and every korg kernel into the
development branches, with a one kernel jump after we do a release
with a kernel (which in this case 3.17 comes with Yocto 1.8). And
that is simply to allow the existing set of three kernels to settle
before refreshing features, moving into another round of development
and preparation for the next release kernel.
Cheers,
Bruce
>
> --
> Cody
>
prev parent reply other threads:[~2014-12-17 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 18:02 bump linux-yocto-dev to 3.18? Cody P Schafer
2014-12-17 18:07 ` Bruce Ashfield [this message]
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=5491C67B.7030901@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dev@codyps.com \
--cc=yocto@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.