From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: Problem with new sign+encrypt code
Date: Mon, 13 May 2002 11:20:41 -0400 [thread overview]
Message-ID: <87n0v4oz06.fsf@alum.wpi.edu> (raw)
In-Reply-To: <877km9ig6h.fsf@graaff.xs4all.nl>
Hans de Graaff <hans@degraaff.org> writes:
> The following patch seems to fix that, but I'm not sure if this is
> the proper fix.
> [...]
Thanks for the fix, It's been applied.
--
Josh Huber
prev parent reply other threads:[~2002-05-13 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 14:39 Hans de Graaff
2002-05-13 15:20 ` Josh Huber [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=87n0v4oz06.fsf@alum.wpi.edu \
--to=huber@alum.wpi.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).