Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] luarocks addon
Date: Mon, 31 Dec 2018 17:57:45 +0100	[thread overview]
Message-ID: <20181231175745.35c7ac37@windsurf> (raw)
In-Reply-To: <20181219081707.1983-1-francois.perrad@gadz.org>

Hello,

On Wed, 19 Dec 2018 09:17:02 +0100, Francois Perrad wrote:

> Francois Perrad (5):
>   luarocks: add buildroot addon
>   lua*: regeneration of *.mk files
>   lua*: regeneration of Config.in
>   lua*: regeneration of hash files
>   pkg-luarocks: add per package upgrade target

I have applied this series, after improving a bit the commit titles and
commit logs and the wording of the change in the Buildroot manual.

Also, in the regeneration of the Config.in files, there were two lines
that got removed that I found should be kept, I'll reply to that patch
specifically.

Best regards,

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

      parent reply	other threads:[~2018-12-31 16:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19  8:17 [Buildroot] [PATCH v3] luarocks addon Francois Perrad
2018-12-19  8:17 ` [Buildroot] [PATCH v3] luarocks: add buildroot addon Francois Perrad
2018-12-31 17:06   ` Thomas Petazzoni
2018-12-19  8:17 ` [Buildroot] [PATCH v3] lua*: regeneration of *.mk files Francois Perrad
2018-12-19  8:17 ` [Buildroot] [PATCH v3] lua*: regeneration of Config.in Francois Perrad
2018-12-31 16:58   ` Thomas Petazzoni
2018-12-19  8:17 ` [Buildroot] [PATCH v3] lua*: regeneration of hash files Francois Perrad
2018-12-19  8:17 ` [Buildroot] [PATCH v3] pkg-luarocks: add per package upgrade target Francois Perrad
2018-12-31 16:57 ` 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=20181231175745.35c7ac37@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