All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/triggerhappy: use git tag instead of hash
Date: Sun, 10 Oct 2021 22:24:25 +0200	[thread overview]
Message-ID: <20211010202425.GQ2081069@scaer> (raw)
In-Reply-To: <20211010201541.1422863-1-fontaine.fabrice@gmail.com>

Fabrice, All,

On 2021-10-10 22:15 +0200, Fabrice Fontaine spake thusly:
> Use release/0.5.0 tag instead of commit hash so
> http://autobuild.buildroot.org/stats will report package as up to date
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/triggerhappy/triggerhappy.hash | 2 +-
>  package/triggerhappy/triggerhappy.mk   | 5 +++--
>  2 files changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/package/triggerhappy/triggerhappy.hash b/package/triggerhappy/triggerhappy.hash
> index ab736cada3..0bb53f9455 100644
> --- a/package/triggerhappy/triggerhappy.hash
> +++ b/package/triggerhappy/triggerhappy.hash
> @@ -1,3 +1,3 @@
>  # Locally calculated
> -sha256  1b3221963b9adca26eacc5442d8c2422cf2072f8adde1dbd691a69b37a583fb1  triggerhappy-b822888066129350e51ad79f1cf307fa38dae4f7.tar.gz
> +sha256  af0fc196202f2d35153be401769a9ad9107b5b6387146cfa8895ae9cafad631c  triggerhappy-0.5.0.tar.gz
>  sha256  8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903  COPYING
> diff --git a/package/triggerhappy/triggerhappy.mk b/package/triggerhappy/triggerhappy.mk
> index f83a557804..bb30e7ce1d 100644
> --- a/package/triggerhappy/triggerhappy.mk
> +++ b/package/triggerhappy/triggerhappy.mk
> @@ -4,8 +4,9 @@
>  #
>  ################################################################################
>  
> -TRIGGERHAPPY_VERSION = b822888066129350e51ad79f1cf307fa38dae4f7
> -TRIGGERHAPPY_SITE = $(call github,wertarbyte,triggerhappy,$(TRIGGERHAPPY_VERSION))
> +TRIGGERHAPPY_VERSION = 0.5.0
> +TRIGGERHAPPY_SITE = \
> +	$(call github,wertarbyte,triggerhappy,release/$(TRIGGERHAPPY_VERSION))
>  TRIGGERHAPPY_LICENSE = GPL-3.0+
>  TRIGGERHAPPY_LICENSE_FILES = COPYING
>  TRIGGERHAPPY_DEPENDENCIES = host-pkgconf
> -- 
> 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

      reply	other threads:[~2021-10-10 20:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10 20:15 [Buildroot] [PATCH 1/1] package/triggerhappy: use git tag instead of hash Fabrice Fontaine
2021-10-10 20:24 ` 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=20211010202425.GQ2081069@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.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 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.