From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host
Date: Fri, 4 Jan 2019 11:10:05 +0100 [thread overview]
Message-ID: <20190104111005.7989095f@windsurf> (raw)
In-Reply-To: <49851202.241713.1546596341117.JavaMail.zimbra@datacom.com.br>
Hello,
On Fri, 4 Jan 2019 08:05:41 -0200 (BRST), Carlos Santos wrote:
> It started when I realized that the trailing slashes in WAF_SITE and
> other host packages. Then Arnout said "we need Config.in.host" and I
> decided to give it a try. It may be a silly explanation but sometimes
> we do things just for fun. :-)
No, no, that's a perfectly fine explanation :-)
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-04 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 17:19 [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host Carlos Santos
2018-12-23 17:19 ` [Buildroot] [PATCH v3 2/3] doc/manual: document the waf packages may need to select host-waf Carlos Santos
2018-12-26 21:31 ` Thomas Petazzoni
2018-12-23 17:19 ` [Buildroot] [PATCH v3 3/3] package/mpv: selec host-waf Carlos Santos
2018-12-26 21:30 ` [Buildroot] [PATCH v3 1/3] package/waf: add a blind Config.in.host Thomas Petazzoni
2018-12-26 21:55 ` Yann E. MORIN
2019-01-03 21:50 ` Thomas Petazzoni
2019-01-03 22:06 ` Yann E. MORIN
2019-01-03 22:14 ` Yann E. MORIN
2019-01-03 23:34 ` Carlos Santos
2019-01-04 8:58 ` Thomas Petazzoni
2019-01-04 10:05 ` Carlos Santos
2019-01-04 10:10 ` Thomas Petazzoni [this message]
2019-01-04 11:06 ` Arnout Vandecappelle
2019-01-04 11:51 ` Yann E. MORIN
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=20190104111005.7989095f@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.