git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug: manpage for `git ls-files` uses <file> instead of <pathspec>

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 13, 2018, 08:03 UTC
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:
Show 5 quoted lines
> 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.

Previous: Lily Ballard
Message 2 of 2 in “Bug: manpage for `git ls-files` uses <file> instead of <pathspec>”
  1. Lily BallardOct 11, 2018
  2. Junio C HamanoOct 13, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.