From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup 0.9 pre-release checkin
Date: Wed, 30 Sep 2009 12:33:34 -0700 [thread overview]
Message-ID: <1254339174-sup-648@masanjin.net> (raw)
In-Reply-To: <1254336855-sup-2395@midna.zekjur.net>
Reformatted excerpts from Michael Stapelberg's message of 2009-09-30:
> http://rubyforge.org/pipermail/sup-talk/2009-September/003189.html
>
> It fixes a crash when opening PGP encrypted (but not signed) emails.
Can you please try the branch i-suck?
About five patches later, I've come in a full circle with this bit of
code.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-09-30 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 18:23 William Morgan
2009-09-30 18:21 ` William Morgan
2009-09-30 18:55 ` Michael Stapelberg
2009-09-30 19:33 ` William Morgan [this message]
2009-09-30 19:53 ` Michael Stapelberg
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=1254339174-sup-648@masanjin.net \
--to=wmorgan-sup@masanjin.net \
/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