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

Re: v2.10.0: ls-tree exit status is always 0, this differs from ls(1)

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 21, 2016, 16:52 UTC
Message-ID
<xmqqr38d9ova.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160921132655.h49HMsHbp%steffen@sdaoden.eu>
Steffen Nurpmeso <steffen@sdaoden.eu> writes:
> I think this behaviour contradicts the manual which strongly links
> ls-tree to ls(1):
Patches to the documentation is very much welcomed.

Somewhere the similarity must end, and actually it ends a lot earlier, as "/bin/ls" takes exact paths while "ls-tree" (or any other Git command for that matter) takes a pathspec pattern, and not having a path that matches the pathspec pattern is not an error condition.

Thanks.
Previous: Steffen NurpmesoNext: Steffen Nurpmeso
Message 2 of 7 in “v2.10.0: ls-tree exit status is always 0, this differs from ls(1)”
  1. Steffen NurpmesoSep 21, 2016
  2. Junio C HamanoSep 21, 2016
  3. Steffen NurpmesoSep 21, 2016
  4. Junio C HamanoSep 21, 2016
  5. Steffen NurpmesoSep 21, 2016
  6. Michael J GruberSep 22, 2016
  7. Steffen NurpmesoSep 22, 2016

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.