How to uniquely identify a given clone of a repository

[Christophe Attias]

Hi,

First thank you all for your answers.
We will try Wagner's tip which seems to be the most likely usable for us.

By the way, Jens, we first thought about your solution (identifying a 
clone by its path) but devs can move their local clones without notifying 
us so that wont work for us.

Thanks all again.
We'll let you know what solution we put in place.

Best regards
Christophe


Wagner Bruna <wagner.bruna at gmail.com> wrote on 13/08/2009 23:13:40:
> Hello,
> 
> Christophe Attias wrote:
> > 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.
> 
> Maybe a local tag on revision 0 could help for that. It'd show up on
> "hg log -r0 --template '{tags}'" and be visible on the web interface,
> and wouldn't be propagated to a new clone. You'd need to manually
> create it and ensure its uniqueness, though.
> 
> Hope that helps,
> Wagner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090814/289b2bf2/attachment.htm