From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Seiderer <ps.report@gmx.net>
Cc: Sergio Prado <sergio.prado@e-labworks.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1 2/2] package/ubus: bump version to f787c97
Date: Sat, 24 Jun 2023 22:53:19 +0200 [thread overview]
Message-ID: <20230624205319.GD24952@scaer> (raw)
In-Reply-To: <20230622165522.16397-2-ps.report@gmx.net>
Peter, All,
On 2023-06-22 18:55 +0200, Peter Seiderer spake thusly:
> Changelog:
>
> - 66baa44b8dee libubus: introduce new status messages
> - b3cd5ab4c010 cli: use UBUS_STATUS_PARSE_ERROR
> - 584f56a23314 cli: improve error logging for call command
> - 2f793a4eb063 lua: add optional path filter to objects() method
> - 2bebf93cd334 ubusd: handle invoke on event object without data
> - 9913aa61de73 ubusd: add lookup command queuing support
> - f787c97b3489 libubus: add missing uloop_fd_delete call in ubus_shutdown
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/ubus/ubus.hash | 2 +-
> package/ubus/ubus.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/ubus/ubus.hash b/package/ubus/ubus.hash
> index 2b7181e5d2..faa2e2626e 100644
> --- a/package/ubus/ubus.hash
> +++ b/package/ubus/ubus.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 275d184006f2f60c9b0172d8fd0ccc8952f182960c0d3d0945be640873c1bef6 ubus-a72457b61df045d3c499a6211362b751710590d7-br1.tar.gz
> +sha256 e3022aa3cf6c38a4d3c0d798d9a9c7069ada063a0a5fe6894b466b71b17ce9cc ubus-f787c97b34894a38b15599886cacbca01271684f-br1.tar.gz
> sha256 a3caa6c0e90c87b7c97c2ac3d0c0d416082ef777215faec2e9b24ea6e68f6988 ubusd_acl.h
> diff --git a/package/ubus/ubus.mk b/package/ubus/ubus.mk
> index fa856fb36a..1f9891411a 100644
> --- a/package/ubus/ubus.mk
> +++ b/package/ubus/ubus.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -UBUS_VERSION = a72457b61df045d3c499a6211362b751710590d7
> +UBUS_VERSION = f787c97b34894a38b15599886cacbca01271684f
> UBUS_SITE = https://git.openwrt.org/project/ubus.git
> UBUS_SITE_METHOD = git
>
> --
> 2.41.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
next prev parent reply other threads:[~2023-06-24 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 16:55 [Buildroot] [PATCH v1 1/2] package/libubox: bump version to 75a3b87 Peter Seiderer
2023-06-22 16:55 ` [Buildroot] [PATCH v1 2/2] package/ubus: bump version to f787c97 Peter Seiderer
2023-06-24 20:53 ` Yann E. MORIN [this message]
2023-06-24 20:53 ` [Buildroot] [PATCH v1 1/2] package/libubox: bump version to 75a3b87 Yann E. MORIN
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=20230624205319.GD24952@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=ps.report@gmx.net \
--cc=sergio.prado@e-labworks.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