From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/32] cgilua: add hash file
Date: Mon, 27 Jul 2015 22:32:38 +0200 [thread overview]
Message-ID: <20150727223238.57961027@free-electrons.com> (raw)
In-Reply-To: <1438023083-19010-1-git-send-email-francois.perrad@gadz.org>
Dear Francois Perrad,
On Mon, 27 Jul 2015 20:50:52 +0200, Francois Perrad wrote:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/cgilua/cgilua.hash | 2 ++
> 1 file changed, 2 insertions(+)
> create mode 100644 package/cgilua/cgilua.hash
All applied except the lua-periphery patch, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-27 20:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 18:50 [Buildroot] [PATCH 01/32] cgilua: add hash file Francois Perrad
2015-07-27 18:50 ` [Buildroot] [PATCH 02/32] copas: " Francois Perrad
2015-07-27 18:50 ` [Buildroot] [PATCH 03/32] coxpcall: " Francois Perrad
2015-07-27 18:50 ` [Buildroot] [PATCH 04/32] dado: " Francois Perrad
2015-07-27 18:50 ` [Buildroot] [PATCH 05/32] lbase64: " Francois Perrad
2015-07-27 18:50 ` [Buildroot] [PATCH 06/32] ljlinenoise: " Francois Perrad
2015-07-27 18:50 ` [Buildroot] [PATCH 07/32] lpeg: " Francois Perrad
2015-07-27 18:50 ` [Buildroot] [PATCH 08/32] lpty: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 09/32] lrandom: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 10/32] lsqlite: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 11/32] lua-cjson: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 12/32] lua-coat: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 13/32] lua-coatpersistent: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 14/32] lua-csnappy: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 15/32] lua-iconv: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 16/32] lua-messagepack: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 17/32] lua-periphery: " Francois Perrad
2015-07-27 20:28 ` Thomas Petazzoni
2015-07-27 18:51 ` [Buildroot] [PATCH 18/32] lua-testmore: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 19/32] luabitop: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 20/32] luacrypto: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 21/32] luaexpat: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 22/32] luafilesystem: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 23/32] luajson: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 24/32] lualogging: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 25/32] luasec: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 26/32] luasocket: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 27/32] luasql-sqlite3: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 28/32] lunit: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 29/32] lzlib: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 30/32] orbit: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 31/32] rings: " Francois Perrad
2015-07-27 18:51 ` [Buildroot] [PATCH 32/32] xavante: " Francois Perrad
2015-07-27 20:32 ` 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=20150727223238.57961027@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