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

Re: [PATCH] doc: document backslash in gitignore patterns

From
Jeff King <peff@peff.net>
Date
Oct 29, 2025, 15:55 UTC
Message-ID
<20251029155559.GA1134232@coredump.intra.peff.net>
In-Reply-To
<20251029153237.GA1133542@coredump.intra.peff.net>
On Wed, Oct 29, 2025 at 11:32:37AM -0400, Jeff King wrote:
> Subject: [PATCH] doc: document backslash in gitignore patterns

Oh, I forgot to mention: obviously gitattributes inherits the same behavior here. I looked at whether it would want a similar patch, but it does not define the pattern format at all, and just punts to "see gitignore(5) for details". I think that's OK. Unlike where we refer to fnmatch(3) here, you cannot even begin to wonder how backslashes are handled by gitattributes without reading gitignore(5). ;)

There's also the "pathspec" entry in gitglossary(7), which does mention fnmatch(3). Though it is even more confusing because of the literal matching that pathspecs do. I don't know if we'd want anything there (and I kind of doubt people get as exotic about patterns there as they would in gitignore).

-Peff
Previous: Jeff KingNext: D. Ben Knoble
Message 17 of 20 in “Probable issue with code/documentation”
  1. Sruteesh KumarOct 10, 2025
  2. match_pathname(): give fnmatch one char of prefix contextJeff King, Oct 14, 2025
  3. Jeff KingOct 14, 2025
  4. Sruteesh KumarOct 22, 2025
  5. Junio C HamanoOct 23, 2025
  6. Sruteesh KumarOct 24, 2025
  7. Jeff KingOct 26, 2025
  8. Jeff KingOct 26, 2025
  9. 0/2 fix "foo**/bar" matching "foobar"Jeff King, Oct 26, 2025
  10. 1/2 match_pathname(): reorder prefix-match checkJeff King, Oct 26, 2025
  11. 2/2 match_pathname(): give fnmatch one char of prefix contextJeff King, Oct 26, 2025
  12. Junio C HamanoOct 26, 2025
  13. Jeff KingOct 27, 2025
  14. Junio C HamanoOct 27, 2025
  15. Jeff KingOct 28, 2025
  16. doc: document backslash in gitignore patternsJeff King, Oct 29, 2025
  17. Jeff KingOct 29, 2025
  18. D. Ben KnobleOct 30, 2025
  19. Jeff KingOct 30, 2025
  20. Ben KnobleOct 30, 2025

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.