On Tue, Jun 29, 2010 at 10:23:30AM +1000, Ben Finney wrote: > Gianluca Montecchi <[email protected]> writes: > > > On Tuesday 29 June 2010 01:02:06 Ben Finney wrote: > > > Can you come up with a simple name that tells the user exactly what > > > the date means? > > > > Of course. > > > > I modified it in > > > > galactica:~/Devel/be-gian> be --version > > > > revision: 0602f53bd0e8e5708235025b16527f7b389e33f5 > > commit date: 2010-06-29 > > See, that's a problem. The user of BE is going to be thinking in terms > of the commits *they* are making. So I don't think “commit date” is too > helpful. > > Better would be a “release date”, if there were such a thing. > > My ideal resolution to this would be for ‘be --version’ to actually show > the version string; but that would require that BE actually gets > released with a version string.
Not necessarily. BE already has the possibility to have a version string, we just need to decide to use it. (and can be something like 0.1) bye Gianluca _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
