From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/4] package/libabseil-cpp: bump version to 20200923.2
Date: Sat, 24 Oct 2020 22:52:41 +0200 [thread overview]
Message-ID: <20201024225241.1c6a68bb@windsurf.home> (raw)
In-Reply-To: <20201021165005.641-1-buildroot@heine.tech>
On Wed, 21 Oct 2020 18:50:01 +0200
Michael Nosthoff via buildroot <buildroot@busybox.net> wrote:
> * removed patch 0003 as it is now in upstream
> * removed patch 0002 as the logic has been reworked
> * adjusted patch 0001 offset
>
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
> ---
> ...0001-force-position-independent-code.patch | 2 +-
> ...g-use-execinfo.h-only-when-available.patch | 63 ---------------
> .../0003-Fix-build-on-riscv32-675.patch | 77 -------------------
> package/libabseil-cpp/libabseil-cpp.hash | 2 +-
> package/libabseil-cpp/libabseil-cpp.mk | 2 +-
> 5 files changed, 3 insertions(+), 143 deletions(-)
> delete mode 100644 package/libabseil-cpp/0002-absl-debugging-use-execinfo.h-only-when-available.patch
> delete mode 100644 package/libabseil-cpp/0003-Fix-build-on-riscv32-675.patch
Series applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-10-24 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 16:50 [Buildroot] [PATCH v2 1/4] package/libabseil-cpp: bump version to 20200923.2 Michael Nosthoff
2020-10-21 16:50 ` [Buildroot] [PATCH v2 2/4] package/re2: bump version to 2020-10-01 Michael Nosthoff
2020-10-21 16:50 ` [Buildroot] [PATCH v2 3/4] package/grpc: bump version to 1.33.1 Michael Nosthoff
2020-10-21 16:50 ` [Buildroot] [PATCH v2 4/4] DEVELOPERS: Add myself for grpc and dependencies Michael Nosthoff
2020-10-24 20:52 ` 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=20201024225241.1c6a68bb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox