Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com From: Chris Faylor Date: Wed, 2 Aug 2000 16:57:31 -0400 To: cygwin-developers AT sources DOT redhat DOT com Subject: Re: setup versioning Message-ID: <20000802165731.A3061@cygnus.com> Reply-To: cygwin-developers AT sources DOT redhat DOT com Mail-Followup-To: cygwin-developers AT sources DOT redhat DOT com References: <200008022040 DOT QAA23436 AT envy DOT delorie DOT com> <20000802165031 DOT B2905 AT cygnus DOT com> <200008022053 DOT QAA23596 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <200008022053.QAA23596@envy.delorie.com>; from dj@delorie.com on Wed, Aug 02, 2000 at 04:53:44PM -0400 On Wed, Aug 02, 2000 at 04:53:44PM -0400, DJ Delorie wrote: >> 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. The old setup had at least 10 source files and I used to force the version change when I made a release. cgf