From: Robert Yang <liezhi.yang@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] make DESCRIPTION support newline
Date: Fri, 28 Jun 2013 15:34:01 +0800 [thread overview]
Message-ID: <51CD3C69.7010803@windriver.com> (raw)
In-Reply-To: <20130628065050.GJ3261@jama>
On 06/28/2013 02:50 PM, Martin Jansa wrote:
> On Fri, Jun 28, 2013 at 10:04:30AM +0800, Robert Yang wrote:
>>
>>
>> On 06/27/2013 12:05 AM, Saul Wold wrote:
>>> On 06/25/2013 08:27 PM, Robert Yang wrote:
>>>>
>>>> Ping for this one.
>>>>
>>> Robert,
>>>
>>> There were some comments on your patch set and I think an issue with the ipk one.
>>>
>>
>> Hi Saul,
>>
>> I think that you meant Martin's comment on the ipk one, Phil had explained to
>> him, and it worked well with the opkg-utils.
>
> I've confused DESCRIPTION and SUMMARY, but I was talking about this
> change:
> http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/commit/?id=7f0a7976c29b34feaf4f6b00f0a63626614d1c7d
>
> And longer description here:
> https://lists.yoctoproject.org/pipermail/yocto/2012-March/007851.html
>
> So please make sure that your change doesn't break it, but with this
> applied it shouldn't.
>
Yes, I had taken the patch, and it doesn't break the opkg-utils.
// Robert
prev parent reply other threads:[~2013-06-28 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 9:00 [PATCH 0/3] make DESCRIPTION support newline Robert Yang
2013-06-19 9:00 ` [PATCH 1/3] package_rpm.bbclass: " Robert Yang
2013-06-19 9:00 ` [PATCH 2/3] package_ipk.bbclass: " Robert Yang
2013-06-19 9:29 ` Martin Jansa
2013-06-19 9:49 ` Richard Purdie
2013-06-19 10:10 ` Phil Blundell
2013-06-19 10:33 ` Enrico Scholz
2013-06-28 3:21 ` Robert Yang
2013-06-19 9:00 ` [PATCH 3/3] package_deb.bbclass: " Robert Yang
2013-06-26 3:27 ` [PATCH 0/3] " Robert Yang
2013-06-26 16:05 ` Saul Wold
2013-06-28 2:04 ` Robert Yang
2013-06-28 6:50 ` Martin Jansa
2013-06-28 7:34 ` Robert Yang [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=51CD3C69.7010803@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=martin.jansa@gmail.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