On Saturday, November 19, 2011, Konstantin Khomoutov <
> On Fri, 18 Nov 2011 12:20:03 -0800
> PJ Weisberg <p...@irregularexpressions.net> wrote:
>> The more I think about it, though, the more I think I could probably
>> get away with using a timestamp for what I had in mind.
> I'm curious about what do you have in mind; could you please explain?
A while ago, someone at $work made a mini-webapp that shows a chart of
which versions of various projects are deployed to which QA servers and
which customer sites. Out-of-date versions (with a lower version number)
are highlighted. One of the newer projects that another team created is
showing "ERR" for the version, because it has a Git SHA1 instead of an SVN
I was looking for the minimal change I could make to make it
Git-compatible, which I thought would be a version number like what's shown
in `git describe'. (Ideally I didn't want to disrupt the layout by using
something much wider than our current 4-digit SVN rev numbers, but that's
not really important.)
Since the main usecases are answering questions like:
Is $foo up to date?
Which customers are WAY out of date?
Does $customer_site have the bugfix we made last week?
I'm pretty sure a datestamp would be enough for the at-a-glance view.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at