Message-ID: <4A4765F2.70206@cwilson.fastmail.fm>
Date: Sun, 28 Jun 2009 08:45:38 -0400
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: [RFC] jpeg library
References: <4A466538.8030007@cwilson.fastmail.fm> <4A46FAA4.2@users.sourceforge.net> <4A470ADF.5010306@cwilson.fastmail.fm> <4A471802.5030001@users.sourceforge.net> <4A475435.1060505@gmail.com>
In-Reply-To: <4A475435.1060505@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Dave Korn wrote:
>   I was just about to say "We could always try and find a security
> vulnerability, that's the only thing that would cause upstream to update
> libjpeg these days!  :)  But then I took a look at the new change.log and it's
> actually crammed with new and improved functionality, so this is an ideal
> opportunity.
> 
>   I think the makes freezing (obsoleting) libjpeg-6b forever with the lossless
> patch incorporated, and just moving to a straight unpatched release of
> libjpeg-7 a no-brainer doesn't it?  What a fortuitous bit of timing!

Yep.  Sometimes you get lucky.  Not often -- that's why it's called luck.

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple