package/erlang-jiffy: bump to version 2.0.1
PATCH 1/1 package/erlang-jiffy: bump to version 2.0.1
Release Notes:
https://github.com/davisp/jiffy/releases/tag/2.0.1
--- package/erlang-jiffy/erlang-jiffy.hash | 2 +- package/erlang-jiffy/erlang-jiffy.mk | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
package/erlang-jiffy/erlang-jiffy.hash +1 -1
@@ -1,3 +1,3 @@ # Locally computed -sha256 d4ef3fe9a231f4fa3d2f5b4be905c2d2a116b96d56433c66b5d7bd2dace5d52c erlang-jiffy-2.0.0.tar.gz +sha256 e5c1951f819f553a34f61f33124b4c8dba1d665d9bba422e15752fe4fb52337d erlang-jiffy-2.0.1.tar.gz sha256 2d1a98e412143fbcdfdaed110614017b267b007252e1b4e121f9fc921edf9ec7 LICENSE
package/erlang-jiffy/erlang-jiffy.mk +1 -1
@@ -4,7 +4,7 @@ # ################################################################################ -ERLANG_JIFFY_VERSION = 2.0.0 +ERLANG_JIFFY_VERSION = 2.0.1 ERLANG_JIFFY_SITE = $(call github,davisp,jiffy,$(ERLANG_JIFFY_VERSION)) ERLANG_JIFFY_LICENSE = Apache-2.0, \ MIT (core), \
Signature · 6 lines
2.47.3 _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Giulio,
Quoted 5 lines · Giulio Benetti
Release Notes:
https://github.com/davisp/jiffy/releases/tag/2.0.1Signed-off-by Giulio Benetti <[email protected]>---
We usually want new patches to not depend on already pending patches in patchwork, so the "proper" way would have been to send this bump squashed together with the previous 2.0.0 one and mark the other on as superseded in patchwork.
Anyway, I applied both this and the 2.0.0 bump to master, thanks! Marcus
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
Hi Marcus,
Quoted 10 lines
Il giorno 15 giu 2026, alle ore 20:26, Marcus Hoffmann <[email protected]> ha scritto:
Hi Giulio,
Quoted 5 lines · Giulio Benetti
Release Notes:
https://github.com/davisp/jiffy/releases/tag/2.0.1Signed-off-by Giulio Benetti <[email protected]>---
We usually want new patches to not depend on already pending patches in patchwork, so the "proper" way would have been to send this bump squashed together with the previous 2.0.0 one and mark the other on as superseded in patchwork.
My bad I haven’t checked patchwork.
Thanks for taking care.
Best regards
Giulio
Quoted 3 lines
Anyway, I applied both this and the 2.0.0 bump to master, thanks! Marcus
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot