From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/strongswan: install libcharon vici header
Date: Thu, 20 Sep 2018 21:10:42 +0200 [thread overview]
Message-ID: <20180920211042.29234e83@windsurf> (raw)
In-Reply-To: <1537456588-17627-2-git-send-email-matthew.weber@rockwellcollins.com>
Hello,
On Thu, 20 Sep 2018 10:16:28 -0500, Matt Weber wrote:
> - Adds patch to install 'libvici.h' if
> --with-dev-headers is configured.
>
> Strongswan currently installs development headers if
> '--with-dev-headers' is configured, except 'libvici.h'.
>
> Original discussion and commit:
> https://wiki.strongswan.org/projects/strongswan/repository/revisions/01c2b62362df88a03c53b748bb4e88631410f326
I don't understand: if there is an upstream commit for this that dates
back from 2 years ago, why do we need to have this patch ?
Also you say "discussion", but I don't see any "discussion" at this URL.
And you resubmitted the same patch at
https://lists.strongswan.org/pipermail/dev/2018-September/001932.html.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-20 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 15:16 [Buildroot] [PATCH 1/2] package/strongswan: install dev headers Matt Weber
2018-09-20 15:16 ` [Buildroot] [PATCH 2/2] package/strongswan: install libcharon vici header Matt Weber
2018-09-20 19:10 ` Thomas Petazzoni [this message]
2018-09-20 20:00 ` Matthew Weber
2018-10-18 18:52 ` Matthew Weber
2018-09-20 19:09 ` [Buildroot] [PATCH 1/2] package/strongswan: install dev headers Thomas Petazzoni
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=20180920211042.29234e83@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.