From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] lpeg-patterns: new package
Date: Tue, 3 Oct 2017 22:03:02 +0200 [thread overview]
Message-ID: <20171003220302.4e08c9b6@windsurf.home> (raw)
In-Reply-To: <20170924161859.10994-1-francois.perrad@gadz.org>
Hello,
On Sun, 24 Sep 2017 18:18:54 +0200, Francois Perrad wrote:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/Config.in | 1 +
> package/lpeg-patterns/Config.in | 8 ++++++++
> package/lpeg-patterns/lpeg-patterns.hash | 2 ++
> package/lpeg-patterns/lpeg-patterns.mk | 14 ++++++++++++++
> 4 files changed, 25 insertions(+)
> create mode 100644 package/lpeg-patterns/Config.in
> create mode 100644 package/lpeg-patterns/lpeg-patterns.hash
> create mode 100644 package/lpeg-patterns/lpeg-patterns.mk
Thanks, but according to the Buildroot manual, all Lua packages must
now start with "lua", i.e lualpeg-patterns or perhaps preferably
lua-lpeg-patterns.
See also commit 75cf694bb0892186a68bd954cef82922d825ca6f from Arnout.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-03 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 16:18 [Buildroot] [PATCH 1/6] lpeg-patterns: new package Francois Perrad
2017-09-24 16:18 ` [Buildroot] [PATCH 2/6] lua-fifo: " Francois Perrad
2017-10-03 20:03 ` Thomas Petazzoni
2017-09-24 16:18 ` [Buildroot] [PATCH 3/6] lua-cqueues: " Francois Perrad
2017-10-03 20:14 ` Thomas Petazzoni
2017-09-24 16:18 ` [Buildroot] [PATCH 4/6] lua-compat53: " Francois Perrad
2017-10-03 20:15 ` Thomas Petazzoni
2017-09-24 16:18 ` [Buildroot] [PATCH 5/6] lua-basexx: " Francois Perrad
2017-10-03 20:16 ` Thomas Petazzoni
2017-09-24 16:18 ` [Buildroot] [PATCH 6/6] lua-http: " Francois Perrad
2017-10-03 20:17 ` Thomas Petazzoni
2017-10-03 20:03 ` 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=20171003220302.4e08c9b6@windsurf.home \
--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