From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 4/4] iw: pkg-config nitpicking
Date: Thu, 27 Sep 2012 19:27:06 -0300 [thread overview]
Message-ID: <5064D2BA.4050102@zacarias.com.ar> (raw)
In-Reply-To: <5064C7E6.3080005@mind.be>
On 09/27/12 18:40, Arnout Vandecappelle wrote:
> Doesn't removing GIT_DIR break version.sh?
Oh yes it does on dirty, my bad for being to 'dd' happy.
I'll resend the whole set once it's decided what to do about pkg-config.
IMHO host-pkg-config can be killed with fire, no need to duplicate it.
pkg-config might be deprecated as per the usual rite, though it's
duplicate functionality and could be just killed being a piggy with glib
deps :)
Regards.
next prev parent reply other threads:[~2012-09-27 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 10:48 [Buildroot] [PATCHv2 1/4] pkgconf: new package Gustavo Zacarias
2012-09-26 10:48 ` [Buildroot] [PATCHv2 2/4] packages: switch to pkgconf Gustavo Zacarias
2012-09-26 10:48 ` [Buildroot] [PATCHv2 3/4] pkg-config: remove package Gustavo Zacarias
2012-09-26 10:48 ` [Buildroot] [PATCHv2 4/4] iw: pkg-config nitpicking Gustavo Zacarias
2012-09-27 21:40 ` Arnout Vandecappelle
2012-09-27 22:27 ` Gustavo Zacarias [this message]
2012-09-28 14:12 ` 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=5064D2BA.4050102@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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