From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] linux-yocto/3.14: introduce versioned recipes
Date: Mon, 31 Mar 2014 15:41:29 -0400 [thread overview]
Message-ID: <5339C4E9.6020103@windriver.com> (raw)
In-Reply-To: <CANyK_8d1KLFkTKm+P4Q5+2N=iLtmpFMcWcMr+V8r-u5g-2axEw@mail.gmail.com>
On 14-03-31 03:39 PM, Paul Barker wrote:
> On 31 March 2014 18:56, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
>> The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
>> the versioned recipes here.
>>
>
> Should this say Yocto 1.6?
Ha. Yes it should!
Bruce
>
next prev parent reply other threads:[~2014-03-31 19:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 17:56 [PATCH 0/5] lnux-yocto: 3.14 updates Bruce Ashfield
2014-03-31 17:56 ` [PATCH 1/5] linux-yocto/3.14: introduce versioned recipes Bruce Ashfield
2014-03-31 19:39 ` Paul Barker
2014-03-31 19:41 ` Bruce Ashfield [this message]
2014-03-31 17:56 ` [PATCH 2/5] linux-libc-headers: make compression format configurable Bruce Ashfield
2014-03-31 17:56 ` [PATCH 3/5] linux-libc-headers: add 3.14 libc headers Bruce Ashfield
2014-03-31 17:56 ` [PATCH 4/5] libc-headers: set TC default to 3.14 Bruce Ashfield
2014-03-31 19:29 ` Khem Raj
2014-03-31 19:33 ` Bruce Ashfield
2014-03-31 19:47 ` Khem Raj
2014-03-31 19:50 ` Bruce Ashfield
2014-04-01 6:42 ` Khem Raj
2014-04-01 12:54 ` Bruce Ashfield
2014-04-01 14:50 ` Martin Jansa
2014-04-01 14:52 ` Bruce Ashfield
2014-04-01 14:54 ` Richard Purdie
2014-04-01 15:41 ` Bruce Ashfield
2014-03-31 17:56 ` [PATCH 5/5] linux-libc-headers: remove 3.10 recipe Bruce Ashfield
2014-03-31 21:09 ` [PATCH 0/5] lnux-yocto: 3.14 updates Bruce Ashfield
2014-03-31 22:30 ` 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=5339C4E9.6020103@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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.