From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 3/9] package/c-icap: add optional support for openldap
Date: Tue, 23 May 2017 15:41:05 +0200 [thread overview]
Message-ID: <20170523154105.5c0de2c2@free-electrons.com> (raw)
In-Reply-To: <20170521214124.20328-3-bernd.kuhls@t-online.de>
Hello,
On Sun, 21 May 2017 23:41:18 +0200, Bernd Kuhls wrote:
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/c-icap/c-icap.mk | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Patches 3 to 9 applied to next. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-23 13:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 21:41 [Buildroot] [PATCH/next 1/9] package/c-icap: fix berkeleydb configure option Bernd Kuhls
2017-05-21 21:41 ` [Buildroot] [PATCH/next 2/9] package/c-icap: fix bzip2 " Bernd Kuhls
2017-05-22 19:53 ` Thomas Petazzoni
2017-05-21 21:41 ` [Buildroot] [PATCH/next 3/9] package/c-icap: add optional support for openldap Bernd Kuhls
2017-05-23 13:41 ` Thomas Petazzoni [this message]
2017-05-21 21:41 ` [Buildroot] [PATCH/next 4/9] package/c-icap: add optional support for pcre Bernd Kuhls
2017-05-21 21:41 ` [Buildroot] [PATCH/next 5/9] package/c-icap: add optional support for libmemcached Bernd Kuhls
2017-05-21 21:41 ` [Buildroot] [PATCH/next 6/9] package/c-icap: remove configure option process-mutexes Bernd Kuhls
2017-05-21 21:41 ` [Buildroot] [PATCH/next 7/9] package/c-icap: bump version to 0.5.2 Bernd Kuhls
2017-05-21 21:41 ` [Buildroot] [PATCH/next 8/9] package/c-icap-modules: bump version to 0.4.5 Bernd Kuhls
2017-05-21 21:41 ` [Buildroot] [PATCH/next 9/9] package/c-icap: add optional support for openssl Bernd Kuhls
2017-05-22 19:53 ` [Buildroot] [PATCH/next 1/9] package/c-icap: fix berkeleydb configure option 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=20170523154105.5c0de2c2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.