From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Profanity - Build with Python Support
Date: Wed, 24 Jul 2019 10:42:10 +0200 [thread overview]
Message-ID: <20190724084210.XOcvifrAUFC8SWKnis76C2RCledm0FCfAAA8B5aFIaw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13307@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
New comment by teldra on void-packages repository
https://github.com/void-linux/void-packages/issues/13307#issuecomment-514538437
Comment:
People are heavily working on OMEMO support in version 0.7.0. I am waiting desperately for this release and will update the package.
Their OMEMO implementation is based on libsignal-c.
next prev parent reply other threads:[~2019-07-24 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 6:43 [ISSUE] " voidlinux-github
2019-07-24 8:42 ` voidlinux-github [this message]
2019-07-24 8:56 ` [ISSUE] [CLOSED] " voidlinux-github
2019-07-24 8:56 ` voidlinux-github
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=20190724084210.XOcvifrAUFC8SWKnis76C2RCledm0FCfAAA8B5aFIaw@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).