From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] do_unpack, do_patch: shift some responsibility around, clean things up
Date: Wed, 01 Sep 2010 18:03:58 -0700 [thread overview]
Message-ID: <4C7EF7FE.8080405@mentor.com> (raw)
In-Reply-To: <AANLkTim4MZ_jPZDnGzV7wKgeC_aQFN_uj2Pjxks2Ms8g@mail.gmail.com>
Khem Raj wrote:
> On Wed, Sep 1, 2010 at 7:57 AM, Chris Larson <clarson@kergoth.com> wrote:
>> On Wed, Sep 1, 2010 at 7:52 AM, Chris Larson <clarson@kergoth.com> wrote:
>>
>>> - Move unpack functions from classes into oe.patch
>>
>> Why do I never notice the typos until after sending it to the list? This
>> should be oe.unpack, of course.
>
> Looks good.
>
> Acked-by: Khem Raj <raj.khem@gmail.com>
>
Put this past a -c patchall -k world and then reproduced the failures
w/o the patch (by hand, hopefully didn't miss anything).
Acked-by: Tom Rini <tom_rini@mentor.com>
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2010-09-02 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 14:52 [PATCH] do_unpack, do_patch: shift some responsibility around, clean things up Chris Larson
2010-09-01 14:57 ` Chris Larson
2010-09-01 15:28 ` Khem Raj
2010-09-02 1:03 ` Tom Rini [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=4C7EF7FE.8080405@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@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 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.