From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] core/legal-info: don't generate big file with all license texts
Date: Sat, 15 Oct 2016 13:12:20 +0200 [thread overview]
Message-ID: <20161015131220.02e0dd8c@free-electrons.com> (raw)
In-Reply-To: <52e41b4a3aab9e9d50ace8aee2501becc5080bb8.1476519329.git.yann.morin.1998@free.fr>
Hello,
On Sat, 15 Oct 2016 10:15:54 +0200, Yann E. MORIN wrote:
> By aggregating all the license files into a single big text-only file
> means we have no way to use license files that are binary blobs (e.g.
> pdf, rtf...).
>
> Just do not generate that big file; if the user still wants it, it is
> very easy to create it afterwards.
>
> Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Luca Ceresoli <luca@lucaceresoli.net>
> ---
> Makefile | 2 --
> package/pkg-generic.mk | 1 -
> package/pkg-utils.mk | 12 ------------
> 3 files changed, 15 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-15 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 8:15 [Buildroot] [PATCH 0/2] core/legal-info: don't generate big file with all license texts Yann E. MORIN
2016-10-15 8:15 ` [Buildroot] [PATCH 1/2] core/legal-info: save empty string when no license file Yann E. MORIN
2016-10-15 10:48 ` Luca Ceresoli
2016-10-15 11:19 ` Thomas Petazzoni
2016-10-15 8:15 ` [Buildroot] [PATCH 2/2] core/legal-info: don't generate big file with all license texts Yann E. MORIN
2016-10-15 9:20 ` Arnout Vandecappelle
2016-10-15 10:54 ` Luca Ceresoli
2016-10-15 11:12 ` 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=20161015131220.02e0dd8c@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.