Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Subject: Re: New setup.exe snapshot available. From: Robert Collins To: Hans Horn Cc: cygwin@cygwin.com In-Reply-To: References: <1047169398.25565.11.camel@localhost> <3.0.5.32.20030308230123.007fd7d0@incoming.verizon.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-v/niR0SQ7O3wVccGKXEm" Organization: Message-Id: <1047417896.6109.46.camel@localhost> Mime-Version: 1.0 Date: 12 Mar 2003 08:24:56 +1100 --=-v/niR0SQ7O3wVccGKXEm Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2003-03-12 at 02:41, Hans Horn wrote: > A look at setup.ini that was newly created, revealed the following: >=20 > setup-timestamp: 1047304219 > setup-version: 2.249.2.5 >=20 > Looks like stale cheese, doesn't it? Not at all. You appear to be making an assumption that is incorrect. The setup-version there is not the version of setup.exe that you *ran*. It's the version of setup.exe that is the *minimum* version that can use the setup.ini file safely. Rob --=20 GPG key available at: . --=-v/niR0SQ7O3wVccGKXEm Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+blQoI5+kQ8LJcoIRAgxyAJ9ybLF0xFK2WAv85flY/9qKihYZrgCfaBF0 Tp12hDN/xOne+66Vlp3yL3k= =avkx -----END PGP SIGNATURE----- --=-v/niR0SQ7O3wVccGKXEm--