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
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Wed, 2 Aug 2000 16:50:32 -0400
To: cygwin-developers AT sources DOT redhat DOT com
Subject: Re: setup versioning
Message-ID: <20000802165031.B2905@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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <200008022040.QAA23436@envy.delorie.com>; from dj@delorie.com on Wed, Aug 02, 2000 at 04:40:59PM -0400

On Wed, Aug 02, 2000 at 04:40:59PM -0400, DJ Delorie wrote:
>
>I was just thinking that the CVS revision of "ChangeLog" might be a
>good automatic version number for setup (aside from the fact that it's
>1.x instead of 2.x, but I can fix that).
>
>Another thought is to auto-tag all the source files, and provide a
>dialog that shows them all, for troubleshooting purposes.  A grep or
>sed could be used to build a .h from all the *.c keywords in their
>comments.
>
>Comments?

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

cgf