From: Junio C Hamano <gitster@pobox.com>
To: Steffen Nurpmeso <steffen@sdaoden.eu>
Cc: git@vger.kernel.org
Subject: Re: v2.10.0: ls-tree exit status is always 0, this differs from ls(1)
Date: Wed, 21 Sep 2016 09:52:41 -0700 [thread overview]
Message-ID: <xmqqr38d9ova.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160921132655.h49HMsHbp%steffen@sdaoden.eu> (Steffen Nurpmeso's message of "Wed, 21 Sep 2016 15:26:55 +0200")
Steffen Nurpmeso <steffen@sdaoden.eu> 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 "ls-tree" (or any
other Git command for that matter) takes a pathspec pattern,
and not having a path that matches the pathspec pattern is not
an error condition.
Thanks.
next prev parent reply other threads:[~2016-09-21 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 13:26 v2.10.0: ls-tree exit status is always 0, this differs from ls(1) Steffen Nurpmeso
2016-09-21 16:52 ` Junio C Hamano [this message]
2016-09-21 19:40 ` Steffen Nurpmeso
2016-09-21 20:39 ` Junio C Hamano
2016-09-21 22:46 ` Steffen Nurpmeso
2016-09-22 11:36 ` Michael J Gruber
2016-09-22 12:57 ` Steffen Nurpmeso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr38d9ova.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=steffen@sdaoden.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox