All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] luaposix: Use github call
Date: Sun, 12 Oct 2014 18:29:46 +0200	[thread overview]
Message-ID: <20141012182946.7db59593@free-electrons.com> (raw)
In-Reply-To: <1413131033-26185-1-git-send-email-maxime.hadjinlian@gmail.com>

Dear Maxime Hadjinlian,

On Sun, 12 Oct 2014 18:23:53 +0200, Maxime Hadjinlian wrote:
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> ---
>  package/luaposix/luaposix.mk | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/package/luaposix/luaposix.mk b/package/luaposix/luaposix.mk
> index 46723a0..13fc266 100644
> --- a/package/luaposix/luaposix.mk
> +++ b/package/luaposix/luaposix.mk
> @@ -5,8 +5,7 @@
>  ################################################################################
>  
>  LUAPOSIX_VERSION = 32
> -LUAPOSIX_SITE = https://github.com/luaposix/luaposix/archive
> -LUAPOSIX_SOURCE = release-v$(LUAPOSIX_VERSION).tar.gz
> +LUAPOSIX_SITE = $(call github,luaposix,luaposix,release-v$(LUAPOSIX_VERSION))
>  LUAPOSIX_LICENSE = MIT
>  LUAPOSIX_LICENSE_FILES = COPYING
>  LUAPOSIX_DEPENDENCIES = luainterpreter host-lua

Why would we want to use git instead of a simple tarball?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-10-12 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 16:23 [Buildroot] [PATCH] luaposix: Use github call Maxime Hadjinlian
2014-10-12 16:29 ` Thomas Petazzoni [this message]
2014-10-12 16:32   ` Maxime Hadjinlian
2014-10-25  0:11 ` Yann E. MORIN
2014-10-25  0:35 ` 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=20141012182946.7db59593@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 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.