From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [for-denzil][PATCH 1/2] curl: enable ssl support
Date: Mon, 16 Jul 2012 11:32:43 -0700 [thread overview]
Message-ID: <50045E4B.7070202@intel.com> (raw)
In-Reply-To: <1342449862-26387-1-git-send-email-koen@dominion.thruhere.net>
On 07/16/2012 07:44 AM, Koen Kooi wrote:
> From: Saul Wold <sgw@linux.intel.com>
>
> This patch enables ssl support for curl to allow git to clone from
> https / ssl sites. We do not want to enable gnutls for native or
> nativesdk, as it adds additional dependency and increase build time
>
> [YOCTO #2532]
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
Thanks, please ping me by the end of Wednesday if you don't see this in:
http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next-1.2.2
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
prev parent reply other threads:[~2012-07-16 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 14:44 [for-denzil][PATCH 1/2] curl: enable ssl support Koen Kooi
2012-07-16 14:44 ` [for-denzil][PATCH 2/2] curl: Use gnutls for target and openssl for native Koen Kooi
2012-07-16 18:32 ` Scott Garman [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=50045E4B.7070202@intel.com \
--to=scott.a.garman@intel.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