[PATCH v3 0/2] ls-tree: exit with non-zero status on error · Jon Seymour <hidden> · 2016-06-15
[PATCH v3 2/2] Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails. · Jon Seymour <hidden> · 2016-06-15
Re: [PATCH v3 2/2] Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails. · Nguyen Thai Ngoc Duy <hidden> · 2016-06-15
Re: [PATCH v3 2/2] Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails. · Jon Seymour <hidden> · 2016-06-15
Re: [PATCH v3 2/2] Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails. · Nguyen Thai Ngoc Duy <hidden> · 2016-06-15
Re: [PATCH v3 2/2] Ensure git ls-tree exits with a non-zero exit code if read_tree_recursive fails. · Jens Lehmann <hidden> · 2016-06-15
[PATCH v3 1/2] Add a test to check that git ls-tree sets non-zero exit code on error. · Jon Seymour <hidden> · 2016-06-15

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

From: Jens Lehmann <hidden>
Date: 2016-06-15 22:51:39

Am 25.07.2011 10:45, schrieb Jon Seymour:

Fair point.

Everyone ok with this revision? If so, I will re-roll v4.

Jens: I added the variable back because the return statement with a
ternary operator needed a line break. Let me know
if there is a better way to format it.

Now the extra variable makes sense to me, so I'm good too.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help