From: James Thomas <jimjoe@gmx.net>
To: 51115@debbugs.gnu.org
Subject: [bug#51115] [PATCH 0/3] Add lurch.
Date: Sun, 10 Oct 2021 14:31:21 +0530 [thread overview]
Message-ID: <87mtnhfe3i.fsf@gmx.net> (raw)
This patchset adds lurch for OMEMO encryption support in libpurple based
programs such as Pidgin. I have tested it (not on Pidgin, but) on a
feature branch of bitlbee-purple:
https://github.com/paretje/bitlbee/tree/feature/lurch
James Thomas (3):
gnu: Add axc.
gnu: Add libomemo.
gnu: Add purple-lurch.
gnu/packages/messaging.scm | 128 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 128 insertions(+)
--
2.32.0
next reply other threads:[~2021-10-10 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 9:01 James Thomas [this message]
2021-10-10 23:39 ` [bug#51115] [PATCH 1/3] Add axc James Thomas
2021-10-10 23:42 ` [bug#51115] [PATCH 2/3] Add libomemo James Thomas
2021-10-10 23:44 ` [bug#51115] [PATCH 3/3] Add purple-lurch James Thomas
2021-11-14 18:35 ` bug#51115: [PATCH 0/3] Add lurch Ludovic Courtès
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=87mtnhfe3i.fsf@gmx.net \
--to=jimjoe@gmx.net \
--cc=51115@debbugs.gnu.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.
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).