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

2016-09-22 Thread Steffen Nurpmeso
Hello, Michael J Gruber wrote: |Steffen Nurpmeso venit, vidit, dixit 22.09.2016 00:46: |> Junio C Hamano wrote: |>|Steffen Nurpmeso writes: ... |>|I think this issue does not need a separate bullet point. The |>|existing

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

2016-09-22 Thread Michael J Gruber
Steffen Nurpmeso venit, vidit, dixit 22.09.2016 00:46: > Junio C Hamano wrote: > |Steffen Nurpmeso writes: > ... > |Sorry, but I did not notice that there was an attached patch when I > |was reading your response for the first time. Risk of using an >

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

2016-09-21 Thread Steffen Nurpmeso
Junio C Hamano wrote: |Steffen Nurpmeso writes: ... |Sorry, but I did not notice that there was an attached patch when I |was reading your response for the first time. Risk of using an |attachment to e-mail ;-) | |I think this issue does not need a

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

2016-09-21 Thread Junio C Hamano
Steffen Nurpmeso writes: > diff --git a/Documentation/git-ls-tree.txt b/Documentation/git-ls-tree.txt > index dbc91f9..8ebeced 100644 > --- a/Documentation/git-ls-tree.txt > +++ b/Documentation/git-ls-tree.txt > @@ -33,6 +33,10 @@ in the current working directory. Note that:

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

2016-09-21 Thread Steffen Nurpmeso
Hello. Junio C Hamano wrote: |Steffen Nurpmeso writes: |> I think this behaviour contradicts the manual which strongly links |> ls-tree to ls(1): | |Patches to the documentation is very much welcomed. The below could serve this purpose. |Somewhere

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

2016-09-21 Thread Junio C Hamano
Steffen Nurpmeso 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

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

2016-09-21 Thread Steffen Nurpmeso
I think this behaviour contradicts the manual which strongly links ls-tree to ls(1): ?0[steffen@wales ]$ ls NEWSS ls: cannot access 'NEWSS': No such file or directory ?2[steffen@wales ]$ git ls-tree --name-only master NEWSS