Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Waf patches series follow-up
Date: Mon, 5 Nov 2018 14:06:19 +0100	[thread overview]
Message-ID: <20181105140619.17df8122@windsurf> (raw)
In-Reply-To: <CAKAx1cjmWvfb6SQnRF11wQvtGo9MNq07P96oPDin+16CrfurZA@mail.gmail.com>

Hello,

On Mon, 5 Nov 2018 10:36:16 +0100, Lionel Orry wrote:

> can anyone have a look at my pending patches on Waf (and other build
> systems)? Here are the links again:
> 
> http://patchwork.ozlabs.org/patch/982373/
> http://patchwork.ozlabs.org/project/buildroot/list/?series=70199

It was on the list of patches I wanted to discuss during the last
Buildroot Developers meeting, as I wanted to chat with Arnout on the
semantic of <pkg>_SUBDIR, but we discussed many other topics and didn't
get to that one.

I'll try to reply on the patch series so that we can keep the
discussion moving.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-11-05 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05  9:36 [Buildroot] Waf patches series follow-up Lionel Orry
2018-11-05 13:06 ` 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=20181105140619.17df8122@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox