Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Before I read this I noticed the revision had changed on SO from the SVN revision to 2010.4.23.1. Just switched to Mercurial from SVN myself and hit this same problem. We used to display the SVN revision on the site, but now that we have no true central repository, displaying a number that can be tied back to the source control system is a challenge.

How is the reverse date format for the site revision managed and then tied back to source?

share|improve this question
This is almost a question for SO – juan Apr 23 '10 at 19:01
I believe it IS a question for SO, not for meta – Andreas Bonini Apr 24 '10 at 12:14
up vote 4 down vote accepted

We are currently using a built in CC.NET labeller that revisions based on date -

It's not a perfect system and I am actually looking for a better labeller that would relate a build back to a mercurial changeset ID. It must be numeric so that we can include this number in our assemblies at build time.

share|improve this answer

But there is a number that can be tied back to the source control system.

[balpha@localhost unicorns-0-5]$ hg tip
changeset:   63:e2024788839c
tag:         tip
user:        balpha
date:        Wed Mar 31 21:29:16 2010 +0200
summary:     Add Stack Overflow message to the website

The 63 needn't be identical on clones of the repo, but the revision hash is.

share|improve this answer
Just​​​ the tip?​​​ – snicker Apr 23 '10 at 20:04
The 63 is only valid as long as your central repo is never replaced, correct? I don't know why this would happen, but I suppose it could. This is what I decided to do with our source...but it bugs me. :) – ranomore Apr 26 '10 at 17:34
@ranomore: Yes, it could. Never rely on the 63. Rely on the e20247... -- that one identifies the changeset no matter what way it reached whichever repo. The idea of DVCS is that there is no real central repo -- it should be replaceable anytime. – balpha Apr 26 '10 at 17:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .