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/luasec: bump to version 1.2.0
Date: Sun, 4 Sep 2022 09:43:01 +0200	[thread overview]
Message-ID: <20220904074301.GS68979@scaer> (raw)
In-Reply-To: <20220903135851.2001980-1-francois.perrad@gadz.org>

François, All,

On 2022-09-03 15:58 +0200, Francois Perrad spake thusly:
> diff LICENSE:
> -LuaSec 1.0.2 license
> -Copyright (C) 2006-2021 Bruno Silvestre, UFG
> +LuaSec 1.2.0 license
> +Copyright (C) 2006-2022 Bruno Silvestre, UFG

This dif-like got patchwork confused:
    https://patchwork.ozlabs.org/project/buildroot/patch/20220903135851.2001980-1-francois.perrad@gadz.org/

Fortuately it seems git-am managed better. :-)

Applied to next, after rewriting the commit log to not include a
diff-like blurb, thanks.

Regards,
Yann E. MORIN.

> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
>  package/luasec/luasec.hash | 4 ++--
>  package/luasec/luasec.mk   | 2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/luasec/luasec.hash b/package/luasec/luasec.hash
> index 1e381612b..3c2b7d803 100644
> --- a/package/luasec/luasec.hash
> +++ b/package/luasec/luasec.hash
> @@ -1,3 +1,3 @@
>  # computed by luarocks/buildroot
> -sha256  7ed5d08aad8f0e8659abb3f43c935da1c898474d4dc121e9edfbeae5c4c67fb0  luasec-1.0.2-1.src.rock
> -sha256  84376baf33cefbcc1e9adbca23fcf87f51c1107956660cda2880feaef86d6075  luasec/LICENSE
> +sha256  82d9ea7d11688a2b11fc1c4549a2e7b0aca00790b49e67a41dac0c81f2890f1c  luasec-1.2.0-1.src.rock
> +sha256  bbf73e23eae7df57a4c4ff33bc23c41a2dc4f8707ba33235c2026d20b41405a7  luasec/LICENSE
> diff --git a/package/luasec/luasec.mk b/package/luasec/luasec.mk
> index 4ace94d16..c7f3a94d9 100644
> --- a/package/luasec/luasec.mk
> +++ b/package/luasec/luasec.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -LUASEC_VERSION = 1.0.2-1
> +LUASEC_VERSION = 1.2.0-1
>  LUASEC_SUBDIR = luasec
>  LUASEC_LICENSE = MIT
>  LUASEC_LICENSE_FILES = $(LUASEC_SUBDIR)/LICENSE
> -- 
> 2.34.1
> 
> _______________________________________________
> 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-09-04  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03 13:58 [Buildroot] [PATCH] package/luasec: bump to version 1.2.0 Francois Perrad
2022-09-04  7:43 ` 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=20220904074301.GS68979@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