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

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

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jul 25, 2011, 22:05 UTC
Message-ID
<CAH3AnrrsWLTn7iCCrp29L9UJN1qbU5SX++6BidenJUQDyJEWNg@mail.gmail.com>
In-Reply-To
<1311631391-12842-1-git-send-email-jon.seymour@gmail.com>
On Tue, Jul 26, 2011 at 8:03 AM, Jon Seymour <jon.seymour@gmail.com> wrote:
>
> This patch uses the return code from read_tree_recursive instead.
Sorry, should be:

This change sets the exit code to 1, if the read_tree_recursive returns non-zero and 0 otherwise.

Previous: Jon Seymour
Message 4 of 4 in “ls-tree: exit with non-zero status on error”
  1. 0/2 ls-tree: exit with non-zero status on errorJon Seymour, Jul 25, 2011
  2. 1/2 Add a test to check that git ls-tree sets non-zero exit code on error.Jon Seymour, Jul 25, 2011
  3. 2/2 Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails.Jon Seymour, Jul 25, 2011
  4. Jon SeymourJul 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.