From: Danilo Bargen <mail@dbrgn.ch>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] package/tealdeer: bump version to 1.6.0
Date: Wed, 12 Oct 2022 00:21:01 +0200 [thread overview]
Message-ID: <20221012002101.02c1f4bf@c3po> (raw)
Signed-off-by: Danilo Bargen <mail@dbrgn.ch>
---
package/tealdeer/tealdeer.hash | 2 +-
package/tealdeer/tealdeer.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/tealdeer/tealdeer.hash b/package/tealdeer/tealdeer.hash
index 0e53174841..b8c9278405 100644
--- a/package/tealdeer/tealdeer.hash
+++ b/package/tealdeer/tealdeer.hash
@@ -1,4 +1,4 @@
# Locally generated
-sha256 42febf9ee84721b9230077d62e2fc51201fd59624d3c776ccc1a634788768a60 tealdeer-1.5.0.tar.gz
+sha256 9b2e9c2d8cbdcf50b3b7865b27a535815874c8d6066f9b7e1ca4d88941065401 tealdeer-1.6.0.tar.gz
sha256 62c7a1e35f56406896d7aa7ca52d0cc0d272ac022b5d2796e7d6905db8a3636a LICENSE-APACHE
sha256 a313b5e62b80a08f3aae0fa62ff3de8482ef55247299eb352ab44f87ef456b1b LICENSE-MIT
diff --git a/package/tealdeer/tealdeer.mk b/package/tealdeer/tealdeer.mk
index c396225098..18b5c35351 100644
--- a/package/tealdeer/tealdeer.mk
+++ b/package/tealdeer/tealdeer.mk
@@ -4,7 +4,7 @@
#
################################################################################
-TEALDEER_VERSION = 1.5.0
+TEALDEER_VERSION = 1.6.0
TEALDEER_SITE = $(call github,dbrgn,tealdeer,v$(TEALDEER_VERSION))
TEALDEER_LICENSE = Apache-2.0 or MIT
TEALDEER_LICENSE_FILES = LICENSE-APACHE LICENSE-MIT
--
2.38.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-10-11 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 22:21 Danilo Bargen [this message]
2022-10-26 21:10 ` [Buildroot] [PATCH 1/1] package/tealdeer: bump version to 1.6.0 Danilo
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=20221012002101.02c1f4bf@c3po \
--to=mail@dbrgn.ch \
--cc=buildroot@buildroot.org \
/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.