Sent from my iPhone... > On Jan 31, 2019, at 09:57, Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Jeremy Huddleston Sequoia <jeremyhu@xxxxxxxxx> writes: > >>> What you probably want instead is >>> >>> # Accommodate for case-insensitive filesystems where *.s would catch >>> !ppc/sha1ppc.S >>> >>> after the `*.[aos]` line. >> >> Thanks for the suggestion. I didn't know that was possible with >> .gitignore. That's a much better solution. > > I still do not see what problem you need a "solution" for in the > first place---I saw a few comments asking it in the thread, but saw > no answer. ppc/sha1ppc.S is already tracked, so any modification > you make in the working tree can be added to the index with "git > add" and "git status" would report when you have modification to > that file in the working tree, without any such extra entry in > .gitignore, no? I originally saw this because the .gitignore was present in the tarball, and we would only update to new versions by pulling in the newer tarball. This resulted in *.S not being included in our repo. When I switched to having upstream be a subtree instead of an extracted tarball, I noticed this difference when comparing the source code difference between the tarball based approach and the git subtree approach. This would have implications for anyone doing something similar or to anyone intending to add new assembly files to the tree (since they wouldn’t show up in status or get added with add -A),
