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

Re: [PATCH] doc: ls-tree paths do not support wildcards

From
Junio C Hamano <gitster@pobox.com>
Date
May 28, 2020, 22:04 UTC
Message-ID
<xmqq4krz3edq.fsf@gitster.c.googlers.com>
In-Reply-To
<pull.796.git.git.1590700996483.gitgitgadget@gmail.com>
"Steven Willis via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 8 quoted lines
> From: Steven Willis <onlynone@gmail.com>
>
> Signed-off-by: Steven Willis <onlynone@gmail.com>
> ---
>     doc: ls-tree paths do not support wildcards
>     
>     The documentation for ls-tree says that paths can be wildcards, but this
>     appears to be incorrect, only raw paths seem to work.
This is not something you would write after the three-dash line.

The documentation does not say paths can be wildcards. It allows a list of "patterns to match" and never says they are wildcards.

I think they take the traditional "leading paths" (i.e. by saying "git ls-tree HEAD t/", you can show all paths that are under t/, and is different from the "raw path" i.e. "git ls-tree HEAD t").

Previous: Junio C HamanoNext: Jeff King
Message 6 of 7 in “doc: ls-tree paths do not support wildcards”
  1. doc: ls-tree paths do not support wildcardsSteven Willis via GitGitGadget, May 28, 2020
  2. Jeff KingMay 28, 2020
  3. Junio C HamanoMay 28, 2020
  4. Jeff KingMay 28, 2020
  5. Junio C HamanoMay 28, 2020
  6. Junio C HamanoMay 28, 2020
  7. Jeff KingMay 28, 2020

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.