From: piotr.kempa@wp.eu
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] PGP INLINE - can't make it work
Date: Tue, 2 Mar 2010 15:19:23 +0100 [thread overview]
Message-ID: <201003021519.23488.piotr.kempa@wp.eu> (raw)
In-Reply-To: <1267538314-sup-6684@midna.zekjur.net>
Sounds cool, I can't wait then. Let's hope the patch is included in 0.11.
Thanks Michael!
Piotr
On Tuesday 02 March 2010 14:59:19 Michael Stapelberg wrote:
> Hi Piotr,
>
> Excerpts from piotr.kempa's message of Di Mär 02 11:49:59 +0100 2010:
> > So, I guess if this functionality is to be included in sup (and I think it
> > doesn't have to be since enigmail just makes broken messages and there's
no
> > reason why anybody should put up with that:) it should not be in crypto.rb
but
> > somewhere else, where the decision is made to even use functions from
> > crypto.rb (like decrypt) on a message. I'm no programmer but I guess it
should
> As mentioned, I wrote a patch to do this. It is currently in review and will
> hopefully be included soon.
>
> Best regards,
> Michael
> _______________________________________________
> sup-talk mailing list
> sup-talk@rubyforge.org
> http://rubyforge.org/mailman/listinfo/sup-talk
>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-03-02 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 17:08 kosmici-atakuja
2010-02-26 17:43 ` Sven Schober
2010-03-02 10:49 ` piotr.kempa
2010-03-02 13:59 ` Michael Stapelberg
2010-03-02 14:19 ` piotr.kempa [this message]
2010-03-08 10:18 ` piotr.kempa
2010-03-08 10:29 ` piotr.kempa
2010-03-08 10:41 ` Michael Stapelberg
2010-03-08 10:50 ` Sven Moritz Hallberg
2010-03-08 11:20 ` piotr.kempa
2010-03-09 17:06 ` Michael Stapelberg
2010-03-10 10:53 ` Piotr Kempa
2010-03-10 11:14 ` Michael Stapelberg
2010-03-10 14:41 ` Piotr Kempa
2010-03-10 21:21 ` Michael Stapelberg
2010-03-02 14:12 ` Sam Hall
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=201003021519.23488.piotr.kempa@wp.eu \
--to=piotr.kempa@wp.eu \
--cc=sup-talk@rubyforge.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