From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] openssl: add version 1.0.0
Date: Tue, 30 Mar 2010 15:43:54 +0200 [thread overview]
Message-ID: <hosv6q$md7$1@dough.gmane.org> (raw)
In-Reply-To: <201003301714.31430.khimov@altell.ru>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 30-03-10 15:14, Roman I Khimov wrote:
> В сообщении от Вторник 30 марта 2010 17:06:14 вы написали:
>> В сообщении от Вторник 30 марта 2010 16:57:33 вы написали:
>>> * DEFAULT_PREFERENCE = "-1", since it might break apps
>>> * enable engines build (and package those separately)
>>
>> Second version fixes engines installation into "/usr/lib/engines" as they
>> should really be installed in "/usr/lib/ssl/engines".
>
> Argh! And it has one patch file missing, so third to come. Sorry for the
> noise.
Could you use --subject-prefix="PATCH v3" with git send-email for that?
It would applying the right one less error prone :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLsgAaMkyGM64RGpERAi05AJ91wSsXlE1QsiwxjJ/qFOpLuxeLXQCfdrM3
VKEJhEx5krDv23c43mEnZZI=
=h+P1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-03-30 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 13:14 [PATCH] openssl: add version 1.0.0 Roman I Khimov
2010-03-30 13:43 ` Koen Kooi [this message]
2010-03-30 13:59 ` Roman I Khimov
-- strict thread matches above, loose matches on Subject: below --
2010-03-30 13:07 Roman I Khimov
[not found] <201003301706.14340.khimov@altell.ru>
2010-03-30 13:06 ` Roman I Khimov
2010-04-28 12:53 ` Marc Olzheim
2010-04-29 5:29 ` Roman I Khimov
2010-05-03 19:59 ` Roman I Khimov
2010-05-04 10:34 ` Marc Olzheim
2010-03-30 12:22 [PATCH] openssl: deal with unpackaged /usr/lib/ssl files Roman I Khimov
2010-03-30 12:22 ` [PATCH] openssl: add version 1.0.0 Roman I Khimov
2010-03-30 12:57 ` Roman I Khimov
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='hosv6q$md7$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.