From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: 45842@debbugs.gnu.org
Subject: [bug#45842] [PATCH] gnu: abseil-cpp: Update to 20200923.2.
Date: Mon, 22 Mar 2021 18:06:12 +0100 [thread overview]
Message-ID: <87ft0nw22j.fsf_-_@gnu.org> (raw)
In-Reply-To: <CA+3U0Zn+Trkgw8oyfjrZ2VG6LAmTEHurG1sy7cGr0H5MqR8rXg@mail.gmail.com> (Greg Hogan's message of "Thu, 11 Mar 2021 16:16:21 -0500")
Hi Greg,
Greg Hogan <code@greghogan.com> skribis:
> From 9d0a4d0d680ff116ca910ef5654690e12aa42ab2 Mon Sep 17 00:00:00 2001
> From: Greg Hogan <code@greghogan.com>
> Date: Mon, 1 Feb 2021 14:01:11 +0000
> Subject: [PATCH 1/2] gnu: abseil-cpp: Update to 20200923.3.
>
> * gnu/packages/cpp.scm (abseil-cpp): Update to 20200923.3.
> [arguments]: Enable external googletest.
> * gnu/packages/patches/abseil-cpp-fix.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Register it.
[...]
> From 9dee38402923238b77a0e9010eb0380849b840ae Mon Sep 17 00:00:00 2001
> From: Greg Hogan <code@greghogan.com>
> Date: Thu, 11 Mar 2021 20:53:15 +0000
> Subject: [PATCH 2/2] gnu: abseil-cpp: Patch sterror_test.
>
> * gnu/packages/patches/abseil-cpp-fix-gtest.patch: Renamed file.
> * gnu/packages/patches/abseil-cpp-fix-strerror_test.patch: New file.
> * gnu/local.mk (dist_patch_DATA): Rename / add files.
> * gnu/packages/cpp.scm (abseil-cpp)[source]: Use files.
Applied both, thanks!
Ludo’.
prev parent reply other threads:[~2021-03-22 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 15:12 [bug#45842] [PATCH] gnu: abseil-cpp: Update to 20200923.2 Greg Hogan
[not found] ` <handler.45842.B.161055074532104.ack@debbugs.gnu.org>
2021-02-01 14:14 ` [bug#45842] Acknowledgement ([PATCH] gnu: abseil-cpp: Update to 20200923.2.) Greg Hogan
2021-03-11 21:16 ` Greg Hogan
2021-03-22 17:06 ` Ludovic Courtès [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=87ft0nw22j.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=45842@debbugs.gnu.org \
--cc=code@greghogan.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.