From: Simon Josefsson <jas@extundo.com>
Subject: Re: [PATCH] make sign/encrypt operate on the whole message
Date: Tue, 22 Jan 2002 23:36:11 +0100 [thread overview]
Message-ID: <iluu1tec8tg.fsf@extundo.com> (raw)
In-Reply-To: <87ofjmcpjx.fsf@paradoxical.net> (Josh Huber's message of "Tue, 22 Jan 2002 11:34:42 -0500")
Josh Huber <huber@alum.wpi.edu> writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Message probably interpreted some of the tags in the diff as, er,
>> tags and chopped stuff up a bit.
>
> Yes, you're probably right. Should have quoted the mml.
>
> Unless someone objects, I'm going to clean up the code and commit it.
Thanks. Comments: It seems to use `recipient' instead of
`recipients', so specifying a recipient doesn't work. Maybe it should
be possible to abbrev these things, so that recip=foo@bar.com would be
sufficient. Also, the manual is out of date wrt to these commands
now. Maybe the `recipients' stuff could be documented as well. :-)
next prev parent reply other threads:[~2002-01-22 22:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 7:38 Josh Huber
2002-01-19 8:05 ` Josh Huber
2002-01-20 0:02 ` Lars Magne Ingebrigtsen
2002-01-22 16:34 ` Josh Huber
2002-01-22 22:36 ` Simon Josefsson [this message]
2002-01-22 22:59 ` Josh Huber
2002-01-20 0:01 ` Lars Magne Ingebrigtsen
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=iluu1tec8tg.fsf@extundo.com \
--to=jas@extundo.com \
/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).