From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Verifying inline gpg signatures
Date: Fri, 21 Mar 2003 16:42:18 -0500 [thread overview]
Message-ID: <2n8yv8wg5h.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <iluznno331c.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 21 Mar 2003 20:58:23 +0100")
Simon Josefsson <jas@extundo.com> writes:
[...]
> Perhaps mm-uu-dissect should be run on all text/plain parts? Or all
> text/.* parts? Opinions?
I think it might be easier to handle these in mm-inline-text.
ShengHuo
prev parent reply other threads:[~2003-03-21 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 20:15 Graham Murray
2003-03-12 20:31 ` Jesper Harder
2003-03-12 20:51 ` Graham Murray
2003-03-12 21:28 ` Jesper Harder
2003-03-12 22:39 ` Graham Murray
2003-03-12 23:20 ` Jesper Harder
2003-03-21 19:58 ` Simon Josefsson
2003-03-21 21:24 ` Jesper Harder
2003-04-24 2:09 ` Jesper Harder
2003-04-24 15:47 ` Simon Josefsson
2003-03-21 21:42 ` ShengHuo ZHU [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=2n8yv8wg5h.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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;
as well as URLs for NNTP newsgroup(s).