From: Kevin Bowersox <kevin.m.bowersox@gmail.com>
To: git@vger.kernel.org
Subject: Potential Issue with ls-tree documentation
Date: Sat, 11 Jan 2020 04:46:33 -0500 [thread overview]
Message-ID: <18b8b8fd-ee38-e1bf-8fae-b719b7b78a75@gmail.com> (raw)
Within the ls-tree documentation for Git found here:
https://git-scm.com/docs/git-ls-tree <https://git-scm.com/docs/git-ls-tree>
It mentions the following:
the behaviour is slightly different from that of "/bin/ls" in that the
<path> denotes just a list of patterns to match, e.g. so specifying
directory name (without |-r|) will behave differently, and order of the
arguments does not matter.
I'm wondering if this statement is accurate. Here is my reasoning:
When using this form of the command:
git ls-tree <tree-ish> [<path>]
the <tree-ish> (assuming this is typically a branch name) must be
specified prior to the path, making the order of the arguments matter
when issuing the command.
If my reasoning is correct I would be glad to submit the changes for
review/merge.
Appreciate any insights.
Kevin Bowersox
next reply other threads:[~2020-01-11 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 9:46 Kevin Bowersox [this message]
2020-01-13 22:33 ` Re* Potential Issue with ls-tree documentation Junio C Hamano
2020-01-13 22:55 ` Elijah Newren
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=18b8b8fd-ee38-e1bf-8fae-b719b7b78a75@gmail.com \
--to=kevin.m.bowersox@gmail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).