From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Kravchuk, Oleksandr" <OKravchuk@luxoft.com>,
"Kravchuk,
Oleksandr (Pelagicore)" <oleksandr.kravchuk@pelagicore.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] curl: upgrade to 7.56.1
Date: Mon, 13 Nov 2017 14:14:51 +0200 [thread overview]
Message-ID: <b1ab5865-28a9-852f-2c6b-c7ca0cba47e6@linux.intel.com> (raw)
In-Reply-To: <6A9F147ED85DE04C91F3A60DD073E94302553D7F@ORO-MBOX-03.luxoft.com>
On 11/13/2017 02:13 PM, Kravchuk, Oleksandr wrote:
> No, they rely on another header file, curl/system.h now, instead of curl/curlbuild.h, which used to be generated during the build time.
>
> Here is an explanation: https://daniel.haxx.se/blog/2017/06/15/target-independent-libcurl-headers/
>
Thanks :) I actually already knew that; the point is that you need to
include the information and the link into the commit message.
Alex
next prev parent reply other threads:[~2017-11-13 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 12:00 [PATCH] curl: upgrade to 7.56.1 Oleksandr Kravchuk
2017-11-13 12:04 ` Alexander Kanavin
[not found] ` <6A9F147ED85DE04C91F3A60DD073E94302553D7F@ORO-MBOX-03.luxoft.com>
2017-11-13 12:14 ` Alexander Kanavin [this message]
2017-11-13 12:32 ` ✗ patchtest: failure for " Patchwork
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=b1ab5865-28a9-852f-2c6b-c7ca0cba47e6@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=OKravchuk@luxoft.com \
--cc=oleksandr.kravchuk@pelagicore.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.