From: Sven Ebenfeld <sven.ebenfeld@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] md5deep: Add Recipe for md5deep package version 4.4
Date: Thu, 28 Aug 2014 21:43:42 +0200 [thread overview]
Message-ID: <53FF866E.8010105@gmail.com> (raw)
In-Reply-To: <20140828143625.GG16066@jama>
Am 28.08.2014 16:36, schrieb Martin Jansa:
> On Thu, Aug 28, 2014 at 11:39:27AM +0200, Sven Ebenfeld wrote:
>> Am 25.08.2014 12:14, schrieb Martin Jansa:
>>> On Mon, Aug 25, 2014 at 09:56:31AM +0200, Sven Ebenfeld wrote:
>>>> I need to build hashdeep/md5deep within OE to include it in my images. This recipe enables OE to cross-compile md5deep. I needed to add the patch as do_configure_qa is complaining about cross-compilation errors otherwise. I added a pull request for the issue with the variable expansion to hashdeep as well.
>>>
>>> Please send this to openembedded-devel@lists.openembedded.org
>>>
>>>
>>
>> Did I understand this right, that I should send the whole patch to
>> OE-Devel ML? Or should I've sent anything else?
>
> Whole patch as it was sent and picked by patchwork:
> http://patchwork.openembedded.org/patch/78901/
>
> it was merged in master-next few days ago.
>
Oh, I didn't see that, that's good news. Thanks!
Is it possible to get that patch into dora and daisy branch as well?
Unfortunately we are still developing in dora branch atm but I hope to
switch to daisy branch in near future.
prev parent reply other threads:[~2014-08-28 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 7:56 [meta-oe][PATCH] md5deep: Add Recipe for md5deep package version 4.4 Sven Ebenfeld
2014-08-25 10:14 ` Martin Jansa
2014-08-25 10:51 ` Sven Ebenfeld
2014-08-28 9:39 ` Sven Ebenfeld
2014-08-28 14:36 ` Martin Jansa
2014-08-28 19:43 ` Sven Ebenfeld [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=53FF866E.8010105@gmail.com \
--to=sven.ebenfeld@gmail.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 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.