Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libcurl: optional verbose strings config
Date: Wed, 1 Feb 2017 22:03:18 +0100	[thread overview]
Message-ID: <20170201220318.06114262@free-electrons.com> (raw)
In-Reply-To: <1485883613-48485-1-git-send-email-matthew.weber@rockwellcollins.com>

Hello,

On Tue, 31 Jan 2017 11:26:53 -0600, Matt Weber wrote:
> From: Judd Meinders <judd.meinders@rockwellcollins.com>
> 
> This patch enables a config to set --enable-verbose during the
> configuration of libcurl.  The option is triggered by setting
> BR2_PACKAGE_LIBCURL_VERBOSE.
> 
> Signed-off-by: Judd Meinders <judd.meinders@rockwellcollins.com>
> Signed-off-by: Matt Weber <matthew.weber@rockwellcollins.com>
> ---
>  package/libcurl/Config.in  | 5 +++++
>  package/libcurl/libcurl.mk | 9 ++++++++-
>  2 files changed, 13 insertions(+), 1 deletion(-)

There's only a 22 KB difference between verbose and non-verbose, so I
wasn't entirely sure a new sub-option was needed. But well, it's still
22 KB, so I've applied your patch. We'll see if others complain about
the additional sub-option for such a small size difference.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2017-02-01 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 17:26 [Buildroot] [PATCH 1/1] libcurl: optional verbose strings config Matt Weber
2017-02-01 21:03 ` Thomas Petazzoni [this message]
     [not found]   ` <CAGReGbRcsp25tZ=YV8+sFp2ZH17XZYhK7AVu2St7C1iKT3nfkA@mail.gmail.com>
2017-02-01 21:21     ` 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=20170201220318.06114262@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox