From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [PATCH] Fix parsing of encrypted messages that contain further multipart elements
Date: Sat, 12 Sep 2009 10:08:50 -0700 [thread overview]
Message-ID: <1252775304-sup-291@masanjin.net> (raw)
In-Reply-To: <6fd87965a2e243b190678edb6c4b9cefbde9ae66.1248369563.git.dato@net.com.org.es>
Reformatted excerpts from Adeodato Sim?'s message of 2009-07-23:
> Amended patch follows, with a better wording that I had seemingly not
> committed. Sorry for the noise.
Not sure why I missed this. Branch crypto-mime-fix, merged into next.
Thanks!
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-09-12 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 17:12 [sup-talk] [RFC] " Adeodato Simó
2009-07-23 17:19 ` [sup-talk] [PATCH] " Adeodato Simó
2009-09-12 17:08 ` William Morgan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1252775304-sup-291@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