Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/lua-cjson: bump to version 2.1.0.10
Date: Mon, 26 Dec 2022 22:13:40 +0100	[thread overview]
Message-ID: <20221226211340.GG2893@scaer> (raw)
In-Reply-To: <20221226074749.143619-1-francois.perrad@gadz.org>

François, All,

On 2022-12-26 08:47 +0100, Francois Perrad spake thusly:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/lua-cjson/Config.in      | 2 +-
>  package/lua-cjson/lua-cjson.hash | 2 +-
>  package/lua-cjson/lua-cjson.mk   | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/lua-cjson/Config.in b/package/lua-cjson/Config.in
> index 9474b3176..1c153fa46 100644
> --- a/package/lua-cjson/Config.in
> +++ b/package/lua-cjson/Config.in
> @@ -12,4 +12,4 @@ config BR2_PACKAGE_LUA_CJSON
>  
>  	  (C-module)
>  
> -	  http://www.kyne.com.au/~mark/software/lua-cjson.php
> +	  https://www.kyne.com.au/~mark/software/lua-cjson.php
> diff --git a/package/lua-cjson/lua-cjson.hash b/package/lua-cjson/lua-cjson.hash
> index b052c5199..5ddc07bcc 100644
> --- a/package/lua-cjson/lua-cjson.hash
> +++ b/package/lua-cjson/lua-cjson.hash
> @@ -1,3 +1,3 @@
>  # computed by luarocks/buildroot
> -sha256  455fa7d07d8ac9d61f68f538958f8e28972256f38b0a1c2740873daf809d1837  lua-cjson-2.1.0.6-1.src.rock
> +sha256  02dea368d07753647c75bd9e6660dd4d06ff7d09956d90d5afc4c3f5b78ed187  lua-cjson-2.1.0.10-1.src.rock
>  sha256  9576e82ef5013fbe80b3bd446a7d9ddd47328baa2186c31d3d885e2a9a8cd31e  lua-cjson/LICENSE
> diff --git a/package/lua-cjson/lua-cjson.mk b/package/lua-cjson/lua-cjson.mk
> index e029dab5c..e08d23006 100644
> --- a/package/lua-cjson/lua-cjson.mk
> +++ b/package/lua-cjson/lua-cjson.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -LUA_CJSON_VERSION = 2.1.0.6-1
> +LUA_CJSON_VERSION = 2.1.0.10-1
>  LUA_CJSON_SUBDIR = lua-cjson
>  LUA_CJSON_LICENSE = MIT
>  LUA_CJSON_LICENSE_FILES = $(LUA_CJSON_SUBDIR)/LICENSE
> -- 
> 2.37.2
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-12-26 21:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26  7:47 [Buildroot] [PATCH] package/lua-cjson: bump to version 2.1.0.10 Francois Perrad
2022-12-26 21:13 ` Yann E. MORIN [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=20221226211340.GG2893@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    --cc=fperrad@gmail.com \
    /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