Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Fri, 17 Mar 2000 16:52:00 -0500
Message-Id:	<200003172152.QAA17582@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	earnie_boyd AT yahoo DOT com
CC:	cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to:	<20000317213617.27882.qmail@web122.yahoomail.com> (message from
	Earnie Boyd on Fri, 17 Mar 2000 13:36:17 -0800 (PST))
Subject:	Re: Setup.exe status
References:	<20000317213617 DOT 27882 DOT qmail AT web122 DOT yahoomail DOT com>

> You mean <ftp>/cygwin/latest don't you, with latest being a link to
> cygwin-1.1.0?  I don't see any reason to change what's already established.

No, I mean that the concept of assigning a version number to the
entire release as a whole will become meaningless with this new
scheme, because packages will be updated asynchronously.  I don't mind
using "latest" as the directory for the release, but there's no point
pointing it to a cygwin-1.1.0 subdirectory.  It would become a real
directory.

- Raw text -