From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v1 1/2] package/ninja: bump version to 1.10.2
Date: Sat, 5 Dec 2020 21:28:30 +0100 [thread overview]
Message-ID: <20201205212830.6cb9158d@windsurf.home> (raw)
In-Reply-To: <20201202194236.1751-1-ps.report@gmx.net>
On Wed, 2 Dec 2020 20:42:35 +0100
Peter Seiderer <ps.report@gmx.net> wrote:
> - rebased 0001-set-minimum-cmake-version-to-3.10.patch
>
> - removed 0002-remove-fdiagnostics-color-from-make-command.patch
> (superseeded by upstream commit [1])
>
> - rebased package/ninja/0003-CMake-fix-object-library-usage.patch
>
> [1] https://github.com/ninja-build/ninja/commit/418d59b8a6054ce9ef1a28c07c41d3a0bb386836
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> ...01-set-minimum-cmake-version-to-3.10.patch | 20 +++---
> ...fdiagnostics-color-from-make-command.patch | 29 --------
> .../0003-CMake-fix-object-library-usage.patch | 67 ++++++++++---------
> package/ninja/ninja.hash | 4 +-
> package/ninja/ninja.mk | 2 +-
> 5 files changed, 49 insertions(+), 73 deletions(-)
> delete mode 100644 package/ninja/0002-remove-fdiagnostics-color-from-make-command.patch
Both applied. Could you keep an eye of meson-based package failures in
the coming days? Updates of Meson have had a tendency to break stuff a
bit in the past. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-12-05 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 19:42 [Buildroot] [PATCH/next v1 1/2] package/ninja: bump version to 1.10.2 Peter Seiderer
2020-12-02 19:42 ` [Buildroot] [PATCH/next v1 2/2] package/meson: bump version to 0.56.0 Peter Seiderer
2020-12-05 20:28 ` Thomas Petazzoni [this message]
2020-12-09 22:50 ` [Buildroot] [PATCH/next v1 1/2] package/ninja: bump version to 1.10.2 Peter Seiderer
2020-12-10 10:36 ` Yegor Yefremov
2020-12-10 19:01 ` Peter Seiderer
2020-12-10 19:19 ` Peter Seiderer
2020-12-10 19:40 ` Peter Seiderer
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=20201205212830.6cb9158d@windsurf.home \
--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 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.