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

Re: [RFD] git glossary: define pathspec

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Nov 29, 2010, 10:21 UTC
Message-ID
<AANLkTi=e5ugMb0fs05Nd5J82=Ua5sg9UrGXztN6rH4=C@mail.gmail.com>
In-Reply-To
<1291025622-15335-1-git-send-email-pclouds@gmail.com>
2010/11/29 Nguyễn Thái Ngọc Duy <pclouds@gmail.com>:
> sure if #3 can do the same.
> ...
> index to tree-based structure.
Words disappear mysteriously. That part says

#1 can match a wildcard pattern literally (say "a*" will match the file named "a*"). This is new to me. I don't know if #3 can do the same.

#2 can't match wildcards, which is known for some time.

#1 and #3 can match index. The famous index does not have directories, so "Documentation" matches that directory well in #2, but won't in #1 and #3. "Documentation/" works in all three. [1] in the previous mail can be used to recreate directories, or we can just move the index to a tree-based structure.

-- 
Duy
Previous: Nguyễn Thái Ngọc DuyNext: Nguyen Thai Ngoc Duy
Message 2 of 4 in “[RFD] git glossary: define pathspec”
  1. Nguyễn Thái Ngọc DuyNov 29, 2010
  2. Nguyen Thai Ngoc DuyNov 29, 2010
  3. Nguyen Thai Ngoc DuyNov 29, 2010
  4. Jonathan NiederNov 29, 2010

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.