On Tuesday 2007 May 01, Junio C Hamano wrote:
Which leaves 'master' right now at v1.5.2-rc1 while 'next' at
v1.5.2-rc1-687-gcb3892c; we might want to do something about
this apparent discrepancy.
It's perfect - I'd say that it's exactly right.
git-describe is for making unique - human readable names for points in
history, not for describing the tree. It makes no difference that A and B
have the same tree, they are different points.
I've always thought of git-describe as being a way of mapping a commit hash to
a nicer looking name. If A and B are different commits then they should have
different names.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com