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

Re: gitignore broken in git 1.7.0.1: slash checks leading dirs

From
JSJiri Slaby <jirislaby@gmail.com>
Date
Mar 5, 2010, 09:29 UTC
Message-ID
<4B90CEDD.6020106@gmail.com>
In-Reply-To
<4B90CBE5.9090102@viscovery.net>
On 03/05/2010 10:16 AM, Johannes Sixt wrote:
> The cited sentence says that the particular check considers only the last
> path component of the pathname.

Thinking about it, there is no way to specify a *filename* no matter where it lies? I.e. patterns such as *.o matches also a/b/test.o/test.c? Am I missing something?

-- 
js
Previous: Américo WangNext: Jonathan Nieder
Message 12 of 19 in “gitignore broken in git 1.7.0.1: slash checks leading dirs”
  1. Jiri SlabyMar 5, 2010
  2. Johannes SixtMar 5, 2010
  3. Jiri SlabyMar 5, 2010
  4. Johannes SixtMar 5, 2010
  5. 1/1 gitignore: do not ignore include/linux/Jiri Slaby, Mar 5, 2010
  6. Jakub NarebskiMar 5, 2010
  7. Jiri SlabyMar 5, 2010
  8. David RientjesMar 10, 2010
  9. Américo WangMar 10, 2010
  10. David RientjesMar 10, 2010
  11. Américo WangMar 8, 2010
  12. Jiri SlabyMar 5, 2010
  13. Jonathan NiederMar 5, 2010
  14. Jiri SlabyMar 5, 2010
  15. Jonathan NiederMar 5, 2010
  16. Jonathan NiederMar 5, 2010
  17. Johannes SixtMar 5, 2010
  18. gitignore.5: Clarify matching rulesJonathan Nieder, Mar 5, 2010
  19. Junio C HamanoMar 5, 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.