On Sat, Aug 09, 2003 at 02:36:01PM -0400, David Dawes wrote: > >Alternatively, we could use the almost same effect by somehow having the > >XFree86.0.log include the latest CHANGELOG entry number. This could be > >done by some preprocessing. > > > >If the date in the first XFree86 line is full, and we have a normal > >release, or it is marked as xx or some other sign, and we are facing a > >CVS checkout. In this case, we use the first number in the line just > >below the XFree86 line, and embed that number in the log message writing > >code. > > I think I can extract the date from the '$XFree86' line in the > CHANGELOG file and add it to the auto-generated xf86Build.h. While > I'm at it, I can adjust the auto-generation of xf86Build.h so that > its modification time doesn't change when its contents don't change. > > I've attached a patch for this.
Nice. But that would mean not using a xxx as day of the month as is currently done (or was last i checked out the tree). > >This would enable us to easily spot when the tree was checked out, and > >would not need us to fool with CVS stuff or so. Naturally this supposes > >that the CHANGELOG file is updated regularly between comits, but this is > >the case anyway. > > It gets updated for most commits, but not necessarily every trivial one. But it gives an idea of the actual checkout. A range of dates at least. Friendly, Sven Luther _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
