Czy próbowałeś usunąć wszystkie spacje w nazwach folderów lub plików z odwróconymi ukośnikami?
*.mode1v3
Foo\ Bar.xcodeproj/
Foo\ Bar.xcodeproj/*.mode1v3
Foo\ Bar.xcodeproj/username.mode1v3
Czy te pliki są już śledzone przez git? Od man gitignore
:
A gitignore file specifies intentionally untracked files that git should ignore.
Note that all the gitignore files really concern only files that are not already
tracked by git; in order to ignore uncommitted changes in already tracked files,
please refer to the git update-index --assume-unchanged documentation.
Dodatkowo, oto niektóre z omówionych wzorów w man gitignore
:
o If the pattern ends with a slash, it is removed for the purpose of the
following description, but it would only find a match with a directory. In
other words, foo/ will match a directory foo and paths underneath it, but will
not match a regular file or a symbolic link foo (this is consistent with the
way how pathspec works in general in git).
o If the pattern does not contain a slash /, git treats it as a shell glob
pattern and checks for a match against the pathname relative to the location of
the .gitignore file (relative to the toplevel of the work tree if not from a
.gitignore file).
o Otherwise, git treats the pattern as a shell glob suitable for consumption by
fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not match
a/in the pathname. For example, "Documentation/*.html" matches
"Documentation/git.html" but not "Documentation/ppc/ppc.html" or
"tools/perf/Documentation/perf.html".
o A leading slash matches the beginning of the pathname. For example, "/*.c"
matches "cat-file.c" but not "mozilla-sha1/sha1.c".
Masz rację. Miałem moment początkujący, w którym spodziewałem się, że pliki zignorowane zostaną zignorowane po prostu na mocy bycia w .gitignore. Ponieważ są już zameldowane, tak nie jest. To wyjaśniło to dla mnie: http://www.gitready.com/beginner/2009/03/06/ignoring-doesnt-remove-a-file.html – pmc255