On Tue, Jun 29, 2010 at 12:16:13AM +0200, Gianluca Montecchi wrote: > I just added the date, since I think that having only the commit-id does not > say anything about how recent is the version. > ... > galactica:~/Devel/be-gian> be --version > > revision: 3748c16a347bc655f624dd5215545c74bd2140da > date: 2010-06-29
I think --version should stay with just the revision id or release string (libbe.version._VERSION). Any extra details should go into full-version, but there you can be as verbose as you want. On Tue, Jun 29, 2010 at 05:34:49PM +1000, Ben Finney wrote: > 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. I believe these are the threads Ben's refering too http://void.printf.net/pipermail/be-devel/2009-July/000202.html http://void.printf.net/pipermail/be-devel/2010-January/000336.html -- This email may be signed or encrypted with GPG (http://www.gnupg.org). The GPG signature (if present) will be attached as 'signature.asc'. For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt
pgpa67fpOalQy.pgp
Description: PGP signature
_______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
