From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/4] package/physfs: new package
Date: Sun, 26 Mar 2017 22:39:04 +0200 [thread overview]
Message-ID: <20170326223904.25cd812b@free-electrons.com> (raw)
In-Reply-To: <20170325215901.15044-1-romain.naour@gmail.com>
Hello,
On Sat, 25 Mar 2017 22:58:58 +0100, Romain Naour wrote:
> Backport a patch from SuperTux project:
> https://github.com/SuperTux/physfs/commit/61d3b63abcba8e9615dcb8a3d1fc026bf7f8d5f8
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> v5: Fix license infos (ThomasP,Arnout,Yann)
> v4: add missing license infos
> Complete lzma license infos (ThomasP)
> v3: new patch
> ---
> DEVELOPERS | 1 +
> package/Config.in | 1 +
> .../physfs/0001-Fix-builds-with-modern-GCC.patch | 38 ++++++++++++++++++++++
> package/physfs/Config.in | 10 ++++++
> package/physfs/physfs.mk | 30 +++++++++++++++++
> 5 files changed, 80 insertions(+)
> create mode 100644 package/physfs/0001-Fix-builds-with-modern-GCC.patch
> create mode 100644 package/physfs/Config.in
> create mode 100644 package/physfs/physfs.mk
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:[~2017-03-26 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 21:58 [Buildroot] [PATCH v5 1/4] package/physfs: new package Romain Naour
2017-03-25 21:58 ` [Buildroot] [PATCH v5 2/4] package/supertux: " Romain Naour
2017-04-15 10:15 ` Thomas Petazzoni
2017-03-25 21:59 ` [Buildroot] [PATCH v5 3/4] package/supertux: fix bug when compiling with PPC altivec vectorization Romain Naour
2017-04-15 10:18 ` Thomas Petazzoni
2017-03-25 21:59 ` [Buildroot] [PATCH v5 4/4] Revert "package/sdl2: disable altivec built-in function for PowerPC" Romain Naour
2017-04-15 10:18 ` Thomas Petazzoni
2017-03-26 20:39 ` 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=20170326223904.25cd812b@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.