Gianluca Montecchi <[email protected]> writes: > On Tue, Jun 29, 2010 at 10:23:30AM +1000, Ben Finney wrote: > > 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)
Of course. Perhaps I wasn't clear that the version string should *mean* something; i.e. that it's a version that the BE developers won't mind hearing about from users and knowing that it refers to a version that was released with an expectation of support longer than a VCS revision. A point made elsewhere in this forum, so I thought I could save the trouble; but I don't mind repeating it again here. -- \ “If sharing a thing in no way diminishes it, it is not rightly | `\ owned if it is not shared.” —Augustine of Hippo (354–430 CE) | _o__) | Ben Finney _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
