"hg describe" extension to get simple cset identifiers [Was: Noob Question: Build number]

Emanuele Aina em at nerd.ocracy.org
Thu Nov 29 20:18:36 UTC 2007


Rob Landley evidenziò:

>>> For my projects, I just declare some repository somewhere the
>>> master, and then use the index in that to refer to commits.
>> 	Why not the global identifier?
> 
> Because "commit 250" is easier to use in discussion than "commit cef5bbd777fa" 
> which is almost impossible to actually remember and which you really have to 
> cut and paste if you're to have any hope of using.
> 
> Plus commit 250 is after 249, so you can estimate newer/older change relative 
> to what went into the central repository when, for "it used to work, when did 
> it break" sort of discussions.  The hash doesn't give you any relation to any 
> other commit.
> 
> I'm not saying it's perfect, I'm just saying the hashes aren't easy to 
> discuss.

It would be great if someone would write a "hg describe" extension 
similar to what git-describe does for GIT, as it seems to give a 
(relatively) simple way to identify commits.

It would solve all your problems without defining "master" repositories 
while keeping unambiguous identifiers.

It could be even folded in "hg identify", avoiding the extra command.

-- 
Buongiorno.
Complimenti per l'ottima scelta.




More information about the Mercurial mailing list