From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Buck To: law@cygnus.com Cc: jbuck@synopsys.com, kriol@FNAL.GOV, egcs@cygnus.com Subject: Re: Direct CVS Access to egcs sources Date: Fri, 16 Jan 1998 01:51:00 -0000 Message-id: <199801151801.KAA03652@atrus.synopsys.com> References: <11971.884881372@hurl.cygnus.com> X-SW-Source: 1998-01/msg00508.html I wrote: > > If you really want to be able to tell what people are running based > > just on the version number, it seems that the version should be updated > > each time a non-documentation file is checked in. Otherwise figuring > > out test results is going to get really confusing. > That's another option. CVS has this kind of capability. Then please do it. > It might be overkill, then again it might not. That's why I'm asking > for opinions :-) I think that it will have a huge advantage. Let's say two people send in test reports for the same platform, with the same version, and one has an additional failure. With cron-generated timestamps, you'll have to search through a whole day's changes to figure out if some patch caused the failure. With an update-on-every-checkin version, you know they are running identical code and you can start looking for subtle system differences. You could lessen the problem by doing a new version string every hour, say, but then people may have identical software that differs only in a version number.