From: Andrei Gherzan <andrei@gherzan.ro>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] dhcp: Update to 4.2.3-P2
Date: Wed, 08 Feb 2012 21:00:18 +0200 [thread overview]
Message-ID: <4F32C642.8030408@gherzan.ro> (raw)
In-Reply-To: <CAP9ODKqaWXbWMx7WRgDEDfqpWM1YPEhbPG_V93mYtd_QVqQJ1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
On 02/08/2012 08:46 PM, Otavio Salvador wrote:
> On Wed, Feb 8, 2012 at 16:40, Andrei Gherzan <andrei@gherzan.ro
> <mailto:andrei@gherzan.ro>> wrote:
>
> ...
>
>
> In my opinion we ought to merge your patch without handling crypto
> issue right now while we set in one way of fixing it.
>
> It seems to me that the fix is to move libcrypto to base_libdir and
> don't touch dhcp for this.
>
>
I don't know why my conclusion line from the last email was erased but
this was my solution as well. I mean a quick and functional one.
@g
[-- Attachment #2: Type: text/html, Size: 1471 bytes --]
next prev parent reply other threads:[~2012-02-08 19:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 16:06 [PATCH] dhcp: Update to 4.2.3-P2 Andrei Gherzan
2012-02-08 16:10 ` Phil Blundell
2012-02-08 16:30 ` Otavio Salvador
2012-02-08 17:00 ` Phil Blundell
2012-02-08 18:40 ` Andrei Gherzan
2012-02-08 18:46 ` Otavio Salvador
2012-02-08 19:00 ` Andrei Gherzan [this message]
2012-02-08 22:20 ` Andrei Gherzan
2012-02-08 22:28 ` Khem Raj
2012-02-08 16:31 ` Mark Hatle
2012-02-08 16:36 ` Andrei Gherzan
2012-02-24 18:27 ` Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2012-02-07 21:27 Andrei Gherzan
2012-02-02 16:20 Andrei Gherzan
2012-02-02 18:32 ` Otavio Salvador
2012-02-02 20:24 ` Andrei Gherzan
2012-02-02 22:07 ` Andrei Gherzan
2012-02-03 10:43 ` Otavio Salvador
2012-02-07 16:20 ` Saul Wold
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=4F32C642.8030408@gherzan.ro \
--to=andrei@gherzan.ro \
--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