From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [dora][PATCH 0/2] Dora backports
Date: Fri, 10 Jan 2014 10:41:56 +0000 [thread overview]
Message-ID: <1389350516.19102.206.camel@ted> (raw)
In-Reply-To: <52CF90CB.3010300@windriver.com>
On Fri, 2014-01-10 at 14:18 +0800, Robert Yang wrote:
> Hi Martin,
>
> Thanks, please see my comments in line.
>
> On 01/06/2014 06:21 PM, Martin Jansa wrote:
> > The following changes since commit e86622a932bbd0acdea67ecfb15c8b06c27353d8:
> >
> > libsoup-2.4: add intltool-native to DEPENDS (2013-12-19 14:59:47 +0000)
> >
> > are available in the git repository at:
> >
> > git://git.openembedded.org/openembedded-core-contrib jansa/dora-backports2
> > http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=jansa/dora-backports2
> >
> > Martin Jansa (1):
> > ltp: set PREFERRED_PROVIDER and rename runtests_noltp.sh script
> >
>
> I will take this.
>
> > Richard Purdie (1):
> > eglibc-initial.inc: Drop duplicate include
> >
>
>
> It seems that this is a trivial fix, I don't think it's a good idea to merge
> it to dora.
Thanks to one of the bitbake patches we backported, this "trivial" issue
is now putting warnings in peoples builds so I think it might be a good
idea to fix it.
Cheers,
Richard
next prev parent reply other threads:[~2014-01-10 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 10:21 [dora][PATCH 0/2] Dora backports Martin Jansa
2014-01-06 10:21 ` [dora][PATCH 1/2] ltp: set PREFERRED_PROVIDER and rename runtests_noltp.sh script Martin Jansa
2014-01-06 10:21 ` [dora][PATCH 2/2] eglibc-initial.inc: Drop duplicate include Martin Jansa
2014-01-10 6:18 ` [dora][PATCH 0/2] Dora backports Robert Yang
2014-01-10 10:41 ` Richard Purdie [this message]
2014-01-10 16:51 ` Mark Hatle
2014-01-11 15:11 ` Koen Kooi
2014-01-10 11:02 ` Martin Jansa
2014-01-13 1:54 ` Robert 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=1389350516.19102.206.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