On 05/12/2011 06:26 AM, Ingo Weinhold wrote:
I am, too. Another possibility would be to include the time down to the nanosecond level -- something like `date -u "+%Y-%m-%d-%k:%M.%N"` could get the job in a way that is quite readable and may not even need to include the hash itself. Just my $0.02.On 2011-05-11 at 23:17:57 [+0200], Niels Sascha Reedijk <niels.reedijk@xxxxxxxxx> wrote:Well, here's my attempt at getting a meaningful revision string (like I put in the other thread). For my tree, with two custom commits, the output would be:Thanks!custom:64fc2d4b5805~2011-05-11 derived from haiku-central:47b487e35b93~2011-05-07 In case of connection troubles, it would be: unverified:64fc2d4b5805~2011-05-11 A 'pure' build would be: haiku-central:b62bc712a76b~2011-05-11I'm still fan of the comparable revision number idea. Maybe the date part can be extended by another component to make it unique? E.g. "2011-05-11-13" would denote the 13th changeset that day. Would that be possible?