From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] upgrade 4 recipes
Date: Thu, 20 Mar 2014 22:30:37 +0000 [thread overview]
Message-ID: <1395354637.27611.27.camel@ted> (raw)
In-Reply-To: <cover.1395281861.git.liezhi.yang@windriver.com>
On Thu, 2014-03-20 at 10:19 +0800, Robert Yang wrote:
> I've test these upgrade on my local AB, they worke well.
We're past feature freeze so these need to wait until 1.7 unless there
is some pressing reason to include them?
Cheers,
Richard
next prev parent reply other threads:[~2014-03-20 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 2:19 [PATCH 0/4] upgrade 4 recipes Robert Yang
2014-03-20 2:19 ` [PATCH 1/4] file: upgrade from 5.16 to 5.17 Robert Yang
2014-03-20 2:19 ` [PATCH 2/4] wget: upgrade from 1.14 to 1.15 Robert Yang
2014-03-20 2:19 ` [PATCH 3/4] automake: upgrade from 1.14 to 1.14.1 Robert Yang
2014-03-20 2:19 ` [PATCH 4/4] mklibs-native: upgrade from 0.1.38 to 0.1.39 Robert Yang
2014-03-20 22:30 ` Richard Purdie [this message]
2014-03-21 0:57 ` [PATCH 0/4] upgrade 4 recipes Robert Yang
-- strict thread matches above, loose matches on Subject: below --
2025-11-17 6:37 [PATCH 0/4] Upgrade " liezhi.yang
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=1395354637.27611.27.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox