From: me <sandidge1@gmail.com>
To: git@vger.kernel.org
Subject: spaces in filenames
Date: Wed, 1 Apr 2026 00:57:54 -0400 [thread overview]
Message-ID: <d8e13917-951c-4bde-8c03-851d727b2e18@gmail.com> (raw)
[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
reply other threads:[~2026-04-01 4:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8e13917-951c-4bde-8c03-851d727b2e18@gmail.com \
--to=sandidge1@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox