delorie.com/archives/browse.cgi | search |
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:40:59 -0400 |
Message-Id: | <200008022040.QAA23436@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | cygwin-developers AT sources DOT redhat DOT com |
Subject: | setup versioning |
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?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |