From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Seiderer <ps.report@gmx.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 1/3] package/libnftnl: bump version to 1.2.0
Date: Sat, 16 Oct 2021 12:26:05 +0200 [thread overview]
Message-ID: <20211016102605.GP4165837@scaer> (raw)
In-Reply-To: <20211014220011.17230-1-ps.report@gmx.net>
Peter, All,
On 2021-10-15 00:00 +0200, Peter Seiderer spake thusly:
> For changes (since 1.1.7) see [1], [2] and [3].
>
> [1] https://lists.netfilter.org/pipermail/netfilter-announce/2020/000246.html
> [2] https://lists.netfilter.org/pipermail/netfilter-announce/2021/000248.html
> [3] https://netfilter.org/projects/libnftnl/files/changes-libnftnl-1.2.0.txt
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/libnftnl/libnftnl.hash | 2 +-
> package/libnftnl/libnftnl.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/libnftnl/libnftnl.hash b/package/libnftnl/libnftnl.hash
> index f22b02af09..9737da1878 100644
> --- a/package/libnftnl/libnftnl.hash
> +++ b/package/libnftnl/libnftnl.hash
> @@ -1,3 +1,3 @@
> # From http://www.netfilter.org/projects/libnftnl/downloads.html
> -sha256 20dbc13f11004aea2c9e479cfb90359cb11fe3446c3140811c18e4ec1648ed8f libnftnl-1.1.7.tar.bz2
> +sha256 90b01fddfe9be8c3245c3ba5ff5a4424a8df708828f92b2b361976b658c074f5 libnftnl-1.2.0.tar.bz2
> sha256 98193898c663001eff2fdcfb676e210c13042bc1a05e8d570c363efa396f8e24 COPYING
> diff --git a/package/libnftnl/libnftnl.mk b/package/libnftnl/libnftnl.mk
> index f4487bdebe..eff93b895f 100644
> --- a/package/libnftnl/libnftnl.mk
> +++ b/package/libnftnl/libnftnl.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -LIBNFTNL_VERSION = 1.1.7
> +LIBNFTNL_VERSION = 1.2.0
> LIBNFTNL_SITE = https://netfilter.org/projects/libnftnl/files
> LIBNFTNL_SOURCE = libnftnl-$(LIBNFTNL_VERSION).tar.bz2
> LIBNFTNL_LICENSE = GPL-2.0+
> --
> 2.33.0
>
> _______________________________________________
> 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
prev parent reply other threads:[~2021-10-16 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 22:00 [Buildroot] [PATCH v1 1/3] package/libnftnl: bump version to 1.2.0 Peter Seiderer
2021-10-14 22:00 ` [Buildroot] [PATCH v1 2/3] package/nftables: bump version to 1.0.0 Peter Seiderer
2021-10-16 10:26 ` Yann E. MORIN
2021-10-14 22:00 ` [Buildroot] [PATCH v1 3/3] package/nftables: disable debug build Peter Seiderer
2021-10-16 10:26 ` Yann E. MORIN
2021-10-22 18:37 ` Peter Korsgaard
2021-10-22 19:25 ` Peter Seiderer
2021-10-22 19:29 ` Peter Seiderer
2021-10-16 10:26 ` 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=20211016102605.GP4165837@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=ps.report@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.