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

Re: [PATCH v3 2/2] Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails.

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 25, 2011, 17:38 UTC
Message-ID
<7vmxg2s1jp.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAH3Anrrbj93briHKpxEjpoVTOnSikQYQyxa4R=C7QKt=punyVw@mail.gmail.com>
Jon Seymour <jon.seymour@gmail.com> writes:
Show 10 quoted lines
> @@ -173,6 +173,7 @@ int cmd_ls_tree(int argc, const char **argv, const
> char *prefix)
>         tree = parse_tree_indirect(sha1);
>         if (!tree)
>                 die("not a tree object");
> -       return read_tree_recursive(tree, "", 0, 0, &pathspec, show_tree, NULL);
> +       ret = read_tree_recursive(tree, "", 0, 0, &pathspec, show_tree, NULL);
>
> +       return ret ? 1 : 0;
>  }
Surely, or "return !!read_tree_recursive(...);" is fine as well.
Previous: Jens Lehmann
Message 9 of 9 in “ls-tree: exit with non-zero status on error”
  1. 0/2 ls-tree: exit with non-zero status on errorJon Seymour, Jul 24, 2011
  2. 1/2 Add a test to check that git ls-tree sets non-zero exit code on error.Jon Seymour, Jul 24, 2011
  3. 2/2 Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails.Jon Seymour, Jul 24, 2011
  4. Nguyen Thai Ngoc DuyJul 25, 2011
  5. Jon SeymourJul 25, 2011
  6. Nguyen Thai Ngoc DuyJul 25, 2011
  7. Andreas SchwabJul 25, 2011
  8. Jens LehmannJul 25, 2011
  9. Junio C HamanoJul 25, 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.