Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
Date:	Tue, 30 Apr 2002 12:34:52 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: MD5 support
Message-ID:	<20020430163452.GA27979@redhat.com>
Reply-To:	cygwin-apps AT cygwin DOT com
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
References:	<FC169E059D1A0442A04C40F86D9BA7600C5F54 AT itdomain003 DOT itdomain DOT net DOT au>
Mime-Version:	1.0
In-Reply-To:	<FC169E059D1A0442A04C40F86D9BA7600C5F54@itdomain003.itdomain.net.au>
User-Agent:	Mutt/1.3.23.1i

On Tue, Apr 30, 2002 at 12:40:43PM +1000, Robert Collins wrote:
>I've uploaded a snapshot (bin & src) that detects corrupt files based on
>md5. It's backward compatible with the current .ini format.
>
>The code needs reorganising before I commit it, this is simply for folk
>to play and test with.
>
>There is -no- UI change at this point. The md5 corruption is silently
>detected (and that will have to change before committing too).

I have upset ready to go for this.  Will it actually break setup.exe if
I check in my changes?  I'm away from a Windows system right now so I
can't check myself.

cgf

- Raw text -