From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: wofi: fix segfaults under musl
Date: Mon, 05 Oct 2020 01:39:13 +0200 [thread overview]
Message-ID: <20201004233913.uPY8-pK8PEg-Mqnw79EkcjBd4NAlexXUunmVLbpQRQk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25347@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
There's a closed pull request on the void-packages repository
wofi: fix segfaults under musl
https://github.com/void-linux/void-packages/pull/25347
Description:
further info: https://todo.sr.ht/~scoopta/wofi/129
next prev parent reply other threads:[~2020-10-04 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 21:41 [PR PATCH] " glats
2020-10-04 21:44 ` glats
2020-10-04 22:39 ` ericonr
2020-10-04 23:39 ` ericonr [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-04 15:44 [PR PATCH] " glats
2020-10-04 21:33 ` [PR PATCH] [Closed]: " glats
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=20201004233913.uPY8-pK8PEg-Mqnw79EkcjBd4NAlexXUunmVLbpQRQk@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).