On Thu, Nov 29, 2007 at 12:32:38PM +0100, Franck Bui-Huu wrote: > Thomas Koeller wrote: > > on my machine I have clones of both the linux-mips and > > Linus' kernel tree. I recently found that git-describe > > behaves differently in those trees: > > [snip] > > > The commit is of course present in both trees. AFAIK the > > 'cannot describe' error shows if there are no tags at all, > > but this is not the case; .git/refs/tags is fully populated. > > Not really, it can happen if the commit you're trying to describe and > all of its parents are not tagged. > > > Has anybody got a clue as to what may be wrong here? > > Is the commit originally part of Linus' tree and was pulled later by > Ralf ? > > If so, it probably means that the commits committed by Ralf in his > tree, which are the tagged ones, have no relationship with the ones > pulled from Linus. I intentionally do not carry the tags from Linus tree in the lmo git tree. Lots of additional tags with little actual use. Whoever would like then can pull from Linus' tree into a lmo clone to get Linus' tags. Back to the original topic - git describe fails even with some of the very old commits of the lmo tree which are known to be tagged so there is something wrong. Ralf
