From: Junio C Hamano <gitster@pobox.com>
Date: Sat, 13 Oct 2018 08:03:12 GMT
Subject: Re: Bug: manpage for `git ls-files` uses <file> instead of <pathspec>
Message-ID: <xmqqzhvi8e9r.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <1539228001.1758106.1538051752.20CB6C51@webmail.messagingengine.com>

Lily Ballard <lily@sb.org> writes:

> I haven’t checked any other commands that the glossary lists as
> taking pathspecs (except `git add`, which does properly list it as
> taking pathspecs), so I don’t know if any of the other commands
> incorrectly list themselves as taking files when they take
> pathspecs.

I do not offhand think of a command that only takes pathname,
including "ls-files".  New users would think "git cmd README" is
taking a single filename "README", and "ls-files" doc uses "file"
in a misguided attempt to be "newbie friendly", but it always has
used that "README" string as a pattern to match paths against.