From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pango: drop PANGO_CONF_ENV variables
Date: Fri, 11 Dec 2015 21:29:32 +0100 [thread overview]
Message-ID: <20151211212932.66dc350f@free-electrons.com> (raw)
In-Reply-To: <1449778645-9112-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Thu, 10 Dec 2015 17:17:25 -0300, Gustavo Zacarias wrote:
> These are completely historic from the initial commit (d106a63d) and
> completely unused.
>
> Two separate builds with/without give nothing relevant with:
>
> $ diff -u pango.cv/config.log pango-1.38.1/config.log|grep ^+
>
> Same applies to removals with:
>
> $ diff -u pango.cv/config.log pango-1.38.1/config.log|grep ^-
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/pango/pango.mk | 53 --------------------------------------------------
> 1 file changed, 53 deletions(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-11 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 20:17 [Buildroot] [PATCH] pango: drop PANGO_CONF_ENV variables Gustavo Zacarias
2015-12-11 20:29 ` Thomas Petazzoni [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=20151211212932.66dc350f@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