From: Mark Wielaard <mark@klomp.org>
To: raif@swiftdsl.com.au
Cc: mauve-discuss@sourceware.org
Subject: Re: patches to ensure names w/ extra spaces are recognized
Date: Mon, 02 Jan 2006 12:29:00 -0000 [thread overview]
Message-ID: <1136204978.8118.4.camel@localhost> (raw)
In-Reply-To: <200601021012.54773.raif@swiftdsl.com.au>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
Hi Raif,
On Mon, 2006-01-02 at 10:12 +1100, Raif S. Naffah wrote:
> pls find attached a patch to existing MessageDigest.getInstance14.java
> and a new Engine.getInstance file to ensure that Provider, Service and
> Algorithm names should be recognized even when they contain extra space
> characters.
This and your next patch for hostnames look good to me.
Tom said you should already have cvs access for Mauve so please feel
free to check these in. (I am currently packing up my machines for
moving so I don't have a good setup atm for quickly doing it myself.)
Thanks,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-01-02 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 23:11 Raif S. Naffah
2006-01-02 12:29 ` Mark Wielaard [this message]
2006-01-02 14:10 ` Raif S. Naffah
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=1136204978.8118.4.camel@localhost \
--to=mark@klomp.org \
--cc=mauve-discuss@sourceware.org \
--cc=raif@swiftdsl.com.au \
/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).