On Tuesday 29 June 2010 01:02:06 Ben Finney wrote: > 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”.
I just followed the --full-version layout: galactica:~/Devel/be-gian> be --full-version revision: 0602f53bd0e8e5708235025b16527f7b389e33f5 date: 2010-06-29 committer: Gianluca storage version: Bugs Everywhere Directory v1.4 galactica:~/Devel/be-gian> > 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 galactica:~/Devel/be-gian> be --full-version revision: 0602f53bd0e8e5708235025b16527f7b389e33f5 commit date: 2010-06-29 committer: Gianluca storage version: Bugs Everywhere Directory v1.4 galactica:~/Devel/be-gian> So --version and --full-version are similar. bye Gianluca _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
