From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/snappy: bump version
Date: Sun, 02 Oct 2016 21:31:29 +0200 [thread overview]
Message-ID: <87eg3ypmy6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1475348688-1805-2-git-send-email-yann.morin.1998@free.fr> (Yann E. MORIN's message of "Sat, 1 Oct 2016 21:04:48 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
For these bump-to-another-git-revision changes I would prefer some
context / details. For bumps to a new release we at least know that the
maintainer thinks the sw is ready to be used. With random git versions
not so much.
E.G. has some important bugfix or new feature been added? Have you used
it yourself? Is the new hash the latest commit in the repo or something
else? ..
Anyway - Committed, thanks.
> ---
> package/snappy/snappy.hash | 2 +-
> package/snappy/snappy.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> diff --git a/package/snappy/snappy.hash b/package/snappy/snappy.hash
> index fc979ae..bb7f104 100644
> --- a/package/snappy/snappy.hash
> +++ b/package/snappy/snappy.hash
> @@ -1,2 +1,2 @@
> # Locally calculated
> -sha256
> d64e434e2ddfe9ae942708747003d489e27f2bfddaa5e9e070da98cb00f660f2
> snappy-1ff9be9b8fafc8528ca9e055646f5932aa5db9c4.tar.gz
> +sha256
> f50719c6dc7103d65df66882a3b4569d598eda251266463eca716928187dc12b
> snappy-32d6d7d8a2ef328a2ee1dd40f072e21f4983ebda.tar.gz
> diff --git a/package/snappy/snappy.mk b/package/snappy/snappy.mk
> index 3e8d603..f491f03 100644
> --- a/package/snappy/snappy.mk
> +++ b/package/snappy/snappy.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
> -SNAPPY_VERSION = 1ff9be9b8fafc8528ca9e055646f5932aa5db9c4
> +SNAPPY_VERSION = 32d6d7d8a2ef328a2ee1dd40f072e21f4983ebda
> SNAPPY_SITE = $(call github,google,snappy,$(SNAPPY_VERSION))
> SNAPPY_LICENSE = BSD-3c
> SNAPPY_LICENSE_FILES = COPYING
> --
> 2.7.4
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-10-02 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 19:04 [Buildroot] [PATCH 1/2] package.snappy: fix static builds Yann E. MORIN
2016-10-01 19:04 ` [Buildroot] [PATCH 2/2] package/snappy: bump version Yann E. MORIN
2016-10-02 19:31 ` Peter Korsgaard [this message]
2016-10-02 19:44 ` Yann E. MORIN
2016-10-02 19:52 ` Peter Korsgaard
2016-10-02 19:19 ` [Buildroot] [PATCH 1/2] package.snappy: fix static builds Peter Korsgaard
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=87eg3ypmy6.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox