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

[PATCH 0/2 v2] ls-tree: exit with non-zero status on error

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jul 24, 2011, 01:07 UTC
Message-ID
<1311469670-15392-1-git-send-email-jon.seymour@gmail.com>

While working with a damaged repository, I noticed that git ls-tree was reporting an error even though it set a zero exit code.

This patch uses the return code from read_tree_recursive instead.
| v2: Amended test per Jens Lehmann's suggestion.
Jon Seymour (2):
  Add a test to check that git ls-tree sets non-zero exit code on
    error.
  Ensure git ls-tree exits with a non-zero exit code if
    read_tree_recursive fails.
 builtin/ls-tree.c               |    6 +++---
 t/t3103-ls-tree-missing-tree.sh |   19 +++++++++++++++++++
 2 files changed, 22 insertions(+), 3 deletions(-)
 create mode 100755 t/t3103-ls-tree-missing-tree.sh
-- 
1.7.6.347.g6a5a9c
Next: Jon Seymour
Message 1 of 7 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. Junio C HamanoJul 24, 2011
  4. Jon SeymourJul 24, 2011
  5. 2/2 Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails.Jon Seymour, Jul 24, 2011
  6. Junio C HamanoJul 24, 2011
  7. Jens LehmannJul 24, 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.