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

spaces in filenames

From
Mme <sandidge1@gmail.com>
Date
Apr 1, 2026, 04:57 UTC
Message-ID
<d8e13917-951c-4bde-8c03-851d727b2e18@gmail.com>
[https://git-scm.com/docs/gitignore#_pattern_format]

so, there are probably a hundred or more pages where this question comes up. The URL I included is just one example.

Ok. fine. there might not be even one more example, but:

the entire tutorial uses namespaces that do not include spaces. and since the real world doesn't ever seem to work that way, I feel you really should include instructions on how to deal with it.

I don't know if this will work/ "or if I should use quotes"/ {or some other arcane method/} :EOF

to delineate that my text has spaces and I can't remove them because users are fundamentally tied to written language syntax.

and your documentation, on your own procedure, doesn't help.

worse than this is that I was sent to your tutorial for help, but from different software that decided to use your process. Now, I know you can't fix them (actually, we both could; it's jellyfin and they are open source, but one step at a time). But, please, can you provide a little more clarity about how Git works? I mean, I use git and I have the question now, I just learned about it because jellyfin is being lazy.

-m
Message 1 of 1 in “spaces in filenames”
  1. meApr 1, 2026

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.