Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/trousers: bump version to 0.3.14
Date: Mon, 20 Aug 2018 23:06:18 +0200	[thread overview]
Message-ID: <20180820230618.7b69ee64@windsurf> (raw)
In-Reply-To: <20180820054734.7709-1-bernd.kuhls@t-online.de>

Hello,

On Mon, 20 Aug 2018 07:47:34 +0200, Bernd Kuhls wrote:
> Removed patches 0001 & 0003, applied upstream.
> Rebased patches 0002 & 0004 and renumbered them.
> Added sha256 hashes for tarball and license file.
> 
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
>  ...r-understands-pie-and-relro-options.patch} | 17 ++--
>  ...-inline-for-read_data-and-write_data.patch | 94 -------------------
>  ...went_r-is-available-before-using-it.patch} |  8 +-
>  ...m-include-limits.h-to-fix-musl-build.patch | 29 ------
>  package/trousers/trousers.hash                |  9 +-
>  package/trousers/trousers.mk                  |  2 +-
>  6 files changed, 20 insertions(+), 139 deletions(-)
>  rename package/trousers/{0002-Check-if-the-compiler-understands-pie-and-relro-options.patch => 0001-Check-if-the-compiler-understands-pie-and-relro-options.patch} (97%)
>  delete mode 100644 package/trousers/0001-Remove-inline-for-read_data-and-write_data.patch
>  rename package/trousers/{0004-Check-that-getpwent_r-is-available-before-using-it.patch => 0002-Check-that-getpwent_r-is-available-before-using-it.patch} (93%)
>  delete mode 100644 package/trousers/0003-tsp_tcsi_param-include-limits.h-to-fix-musl-build.patch

Applied to next, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-08-20 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20  5:47 [Buildroot] [PATCH/next 1/1] package/trousers: bump version to 0.3.14 Bernd Kuhls
2018-08-20 21:06 ` 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=20180820230618.7b69ee64@windsurf \
    --to=thomas.petazzoni@bootlin.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