How to uniquely identify a given clone of a repository

[Christophe Attias]

Hi All,

We are trying to get our developers using Mercurial in the development 
cycle.
But we are looking for a way to uniquely identify a given clone of a 
repository. 
I'm not talking about the way to identify a repository by its first 
revision (using hg log -r0 --template '{node}') because in this case all 
clones will have the same id.

We want to be able to uniquely identify each clone that has been done by 
developers.
The main purpose of this is for integration management. 
For example we want to give the possibility to devs to register their 
local clone on a given bug number.

Saying : "Ok I'm going to work on this bug #123 and on bug #456 and for 
this I'm going to use one given clone of the main repository"
So we need to register the given clone on an external application to say 
that it's main purpose is to solve bug #123 and #456 so that when the dev 
will push or pull his changes we'll keep track of what is solved in this 
clone.
We could do this afterwards and bind the bug numbers to the tip changset 
of the repository but we often need to do it prior to all devs so when 
there is no specific changset in this clone.

I'm not sure to make myself clear on that :)

So is it possible to uniquely identify a clone natively in Mercurial ?
Or do we have to implement some hook ? Is there a best practice to do this 
?

Thanks a lot

Best regards
Christophe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090813/afc78715/attachment.htm