Hi, please assign version numbers 2036 and 2037 to the last daily build CVS kernel stable and unstable versions... That will make it a lot easier to refer to versions e.g. in bugzilla. And people will be able to use VER to get a hint of what version they are using :-). We have been sitting with daily CVS soup for months now, this really makes comparing versions hard. And there is no changelog either - collecting change information from CVS notes is a really tedious thing to do... Anyway, please start the new year with a new version number. Thanks :-).
Of course there will be 2036-cvs and 2037-cvs daily builds after that, but still we will have ONE exact notion of the 2036 and 2037 RELEASE version (e.g. for sf.net download?). People can use those for testing and can for example compare them to the daily CVS updates later in 2006. Doing a binary CVS version search should only be needed as a second step and of course it would then be necessary to calculate the middle day between two dates ;-). You get the idea, I would really be happy to see new real VER version numbers to be used from time to time :-). By the way, VER could also show the version STRING, but that one is only available through a FreeDOS specific API... Other news: Well, enjoy the change-of-year today :-) Eric PS: You could also enjoy my new version of my old crappy mausmenu mini menu system in my usual download area ;-). ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel