From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/delve: bump to version 1.6.1
Date: Sun, 6 Jun 2021 22:59:41 -0700 [thread overview]
Message-ID: <CA+h8R2r3CnJ75ZgYjHSP7iKh=sT937V2_GjKvrjxZeu33h81ig@mail.gmail.com> (raw)
In-Reply-To: <20210530064815.1173206-1-christian@paral.in>
Hi Thomas,
This delve 1.6.1 version change was mentioned in the version update
email you just sent:
On Sat, May 29, 2021 at 11:48 PM Christian Stewart <christian@paral.in> wrote:
>
> Signed-off-by: Christian Stewart <christian@paral.in>
> ---
> package/delve/delve.hash | 4 ++--
> package/delve/delve.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/delve/delve.hash b/package/delve/delve.hash
> index e8bb9c37ad..3d117813c6 100644
> --- a/package/delve/delve.hash
> +++ b/package/delve/delve.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 f8bbaecdfc9d1ff6148900d3dea44b6dd06a7f0197be4e9a75c289b7f62682ab delve-1.5.0.tar.gz
> -sha256 778864b990007e8cef6633f8c372dd05bac1fada6cf67b008afb1483f83b38f5 LICENSE
> +sha256 e73f7fc063632268d3bdf53486aeafd98cceb8f86f4af56903dedfebaefe690d delve-1.6.1.tar.gz
> +sha256 778864b990007e8cef6633f8c372dd05bac1fada6cf67b008afb1483f83b38f5 LICENSE
> diff --git a/package/delve/delve.mk b/package/delve/delve.mk
> index f574bc5c08..6c346552a4 100644
> --- a/package/delve/delve.mk
> +++ b/package/delve/delve.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -DELVE_VERSION = 1.5.0
> +DELVE_VERSION = 1.6.1
> DELVE_SITE = $(call github,go-delve,delve,v$(DELVE_VERSION))
> DELVE_LICENSE = MIT
> DELVE_LICENSE_FILES = LICENSE
> --
> 2.31.1
>
Best regards,
Christian Stewart
next prev parent reply other threads:[~2021-06-07 5:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 6:48 [Buildroot] [PATCH 1/1] package/delve: bump to version 1.6.1 Christian Stewart
2021-06-07 5:59 ` Christian Stewart [this message]
2021-07-18 20:41 ` Thomas Petazzoni
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='CA+h8R2r3CnJ75ZgYjHSP7iKh=sT937V2_GjKvrjxZeu33h81ig@mail.gmail.com' \
--to=christian@paral.in \
--cc=buildroot@busybox.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.