From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 15 Nov 2011 23:20:52 GMT
Subject: Re: odd name-rev behavior?
Message-ID: <7vpqgtt1kb.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20111115211514.GE27706@comcast.net>

Tim Walberg <twalberg@comcast.net> writes:

> Never noticed this before - is this expected? It doesn't seem to
> match documentation, in any case...
>
> Basically, 'git name-rev --all' lists a lot of lines that are
> marked as "undefined", and most, if not all, of the objects
> represented are trees, not commits... I wouldn't have expected
> name-rev to follow the link from a commit to a tree and try to
> process that result...

I wouldn't either, but this does not look like a recent breakage. v1.6.0
seems to show the same broken behaviour.