Gianluca Montecchi <[email protected]> writes: > galactica:~/Devel/be-gian> be --version > > revision: 3748c16a347bc655f624dd5215545c74bd2140da > date: 2010-06-29 > > galactica:~/Devel/be-gian> > --- > > That I think is clearer.
It would be clearer if the date made clear *what* date is being expressed. An unadorned “date” usually means *today's* date; any other date is context-dependent. The user can't really be expected to deduce “the date when this code was committed to the VCS” as opposed to, say, “the date when this code was packaged”. Can you come up with a simple name that tells the user exactly what the date means? -- \ “We must respect the other fellow's religion, but only in the | `\ sense and to the extent that we respect his theory that his | _o__) wife is beautiful and his children smart.” —Henry L. Mencken | Ben Finney _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
