From: "Frank Ch. Eigler" <fche@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: imported gnu.crypto
Date: Thu, 22 Jan 2004 20:07:00 -0000 [thread overview]
Message-ID: <20040122200745.GA18986@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 308 bytes --]
Hi -
We have received export clearance to import gnu.crypto into rhug.
I've just committed a "first draft" for someone more expert with
rhug conventions to revise.
Since gnu.crypto includes at least parts of BouncyCastle, it may
obsolete the current conditional top-level configury for the latter.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-01-22 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 20:07 Frank Ch. Eigler [this message]
2004-01-22 20:30 ` Anthony Green
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=20040122200745.GA18986@redhat.com \
--to=fche@redhat.com \
--cc=rhug-rhats@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).