From: Ralph Seichter <abbot@monksofcool.net>
To: notmuch@notmuchmail.org
Subject: Re: Autocrypt support
Date: Thu, 11 Apr 2019 18:51:42 +0200 [thread overview]
Message-ID: <871s28bi3l.fsf@ra.horus-it.com> (raw)
In-Reply-To: <87pnpsa79g.fsf@fifthhorseman.net>
* Daniel Kahn Gillmor:
> [...] if you'd like to help me strategize about next steps for getting
> autocrypt support into notmuch itself, i'd welcome the collaboration.
I'd be willing to help if you think I can actually be of use to you. ;-)
I have, as of today, not even looked at the Notmuch architecture and
source code. I do know a reasonable amount about GnuPG, RFC 5322 et al,
though.
-Ralph
prev parent reply other threads:[~2019-04-11 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 14:01 Autocrypt support Ralph Seichter
2019-04-11 15:31 ` Daniel Kahn Gillmor
2019-04-11 16:51 ` Ralph Seichter [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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s28bi3l.fsf@ra.horus-it.com \
--to=abbot@monksofcool.net \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).