git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: odd name-rev behavior?

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 15, 2011, 23:20 UTC
Message-ID
<7vpqgtt1kb.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20111115211514.GE27706@comcast.net>
Tim Walberg <twalberg@comcast.net> writes:
Show 8 quoted lines
> 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.

Previous: Tim WalbergNext: Junio C Hamano
Message 2 of 5 in “odd name-rev behavior?”
  1. Tim WalbergNov 15, 2011
  2. Junio C HamanoNov 15, 2011
  3. Junio C HamanoNov 15, 2011
  4. Tim WalbergNov 16, 2011
  5. Junio C HamanoNov 16, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.