From: Efraim Flashner <efraim@flashner.co.il>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: 69539-done@debbugs.gnu.org
Subject: bug#69539: [PATCH]: Update webkitgtk to 2.42.5
Date: Fri, 8 Mar 2024 11:36:08 +0200 [thread overview]
Message-ID: <ZercCBhSurb4X2-U@3900XT> (raw)
In-Reply-To: <87h6hmwaau.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
Thanks. I found a bug report about it failing to build on i686 so I
added a snippet for that. Patch pushed!
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-03-08 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 10:39 [bug#69539] [PATCH]: Update webkitgtk to 2.42.5 André A. Gomes
2024-03-08 9:36 ` Efraim Flashner [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZercCBhSurb4X2-U@3900XT \
--to=efraim@flashner.co.il \
--cc=69539-done@debbugs.gnu.org \
--cc=andremegafone@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).