Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Wed, 2 Aug 2000 16:53:44 -0400
Message-Id: <200008022053.QAA23596@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sources DOT redhat DOT com
In-reply-to: <20000802165031.B2905@cygnus.com> (message from Chris Faylor on
	Wed, 2 Aug 2000 16:50:32 -0400)
Subject: Re: setup versioning
References: <200008022040 DOT QAA23436 AT envy DOT delorie DOT com> <20000802165031 DOT B2905 AT cygnus DOT com>


> The "old" setup.exe just used a $Revision$ tag in setup.c as well
> as time and date.

The old setup also had basically only one source file.  The new setup
has many, so there's a good chance that any given file won't be
touched during an update.  The only one I could think of was
ChangeLog, which almost always changes when setup changes.