From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: workrave: update to 1.10.34
Date: Mon, 04 Nov 2019 19:33:57 +0100 [thread overview]
Message-ID: <20191104183357.HYh6dcoi11AWRxRRrPUesawQaD5UlB7FJuUwL9xre-o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16094@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 210 bytes --]
There's a merged pull request on the void-packages repository
workrave: update to 1.10.34
https://github.com/void-linux/void-packages/pull/16094
Description:
Add missing SONAME
Fix musl build, thanks to q66
prev parent reply other threads:[~2019-11-04 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 2:25 [PR PATCH] " voidlinux-github
2019-11-04 2:55 ` [No Merge] " voidlinux-github
2019-11-04 2:57 ` voidlinux-github
2019-11-04 2:58 ` [PR PATCH] [Updated] " voidlinux-github
2019-11-04 3:00 ` voidlinux-github
2019-11-04 4:02 ` voidlinux-github
2019-11-04 18:33 ` voidlinux-github [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=20191104183357.HYh6dcoi11AWRxRRrPUesawQaD5UlB7FJuUwL9xre-o@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).