From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/knock: bump version
Date: Sun, 31 Jan 2016 08:23:38 +0100 [thread overview]
Message-ID: <20160131082338.4caf63b8@free-electrons.com> (raw)
In-Reply-To: <1454196253-15434-1-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sun, 31 Jan 2016 00:24:13 +0100, Bernd Kuhls wrote:
> -KNOCK_VERSION = 0.7
> -KNOCK_SITE = http://www.zeroflux.org/proj/knock/files
> +KNOCK_VERSION = 258a27e5a47809f97c2b9f2751a88c2f94aae891
> +KNOCK_SITE = $(call github,jvinet,knock,$(KNOCK_VERSION))
> +KNOCK_AUTORECONF = YES
What is the motivation for switch from a tarball release to an
apparently random Git commit on the Github repo? This should have been
explained in the commit log.
Thanks :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-01-31 7:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 23:24 [Buildroot] [PATCH 1/1] package/knock: bump version Bernd Kuhls
2016-01-31 7:23 ` Thomas Petazzoni [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=20160131082338.4caf63b8@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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