* Issues with gitattributes pattern matching
@ 2018-12-12 8:23 Sebastian Schuberth
0 siblings, 0 replies; only message in thread
From: Sebastian Schuberth @ 2018-12-12 8:23 UTC (permalink / raw)
To: git
Hi,
after reading though [1] and [2] again, I believe a pattern in
.gitattributes like
*/src/*/assets/**/*-expected-* text eol=lf
should match a committed file at
reporter/src/funTest/assets/NPM-is-windows-1.0.2-expected-NOTICE
In other words, "**" should be able to match "nothing", but it doesn't
seem to do in my case.
To cross-check, assuming that ls-files supports the same patterns, running
git ls-files "*/src/*/assets/**/*-expected-*"
indeed does not list the committed file at
reporter/src/funTest/assets/NPM-is-windows-1.0.2-expected-NOTICE
for me. Tested with Git 2.20 on Windows and Git 2.19.2 on Linux. Is it a
documentation error or a bug in Git?
[1] https://git-scm.com/docs/gitattributes
[2] https://git-scm.com/docs/gitignore#_pattern_format
--
Sebastian Schuberth
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-12-12 8:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-12-12 8:23 Issues with gitattributes pattern matching Sebastian Schuberth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).