From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lft: new package
Date: Fri, 13 May 2016 23:34:27 +0200 [thread overview]
Message-ID: <20160513233427.43dbe4e1@free-electrons.com> (raw)
In-Reply-To: <1462300214-8562-1-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Tue, 3 May 2016 15:30:14 -0300, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/Config.in | 1 +
> package/lft/0001-no-strip.patch | 19 +++++++++++++++++++
> package/lft/0002-no-incdir.patch | 27 +++++++++++++++++++++++++++
> package/lft/Config.in | 10 ++++++++++
> package/lft/lft.hash | 2 ++
> package/lft/lft.mk | 19 +++++++++++++++++++
> 6 files changed, 78 insertions(+)
> create mode 100644 package/lft/0001-no-strip.patch
> create mode 100644 package/lft/0002-no-incdir.patch
> create mode 100644 package/lft/Config.in
> create mode 100644 package/lft/lft.hash
> create mode 100644 package/lft/lft.mk
I've changed the license name from VOSCOM to the more complete "VOSTROM
Public License for Open Source", which is the complete license name
found in the COPYING file. And then I've applied to next. Thanks!
I guess the chance of seeing the patches merged upstream is pretty
small, unfortunately :/ Have you talked with upstream about the silly
form-based download method?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-13 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 18:30 [Buildroot] [PATCH] lft: new package Gustavo Zacarias
2016-05-13 21:34 ` Thomas Petazzoni [this message]
2016-05-13 22:07 ` Gustavo Zacarias
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=20160513233427.43dbe4e1@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.