Hello, On 25/08/15 18:48, markdblackwell wrote: > Per > https://www.kernel.org/pub/software/scm/git/docs/gitignore.html > > "A gitignore file specifies intentionally untracked files that Git > should ignore. Files already tracked by Git are not affected" > > Aug 23, 2015; 6:21am, James Lowe wrote: >> I had similar problems when trying to add snippets in the doc for >> midi, i.e. any snippet ending in "-midi.ly" > > Mark D. Blackwell wrote: >> Because of these patterns in the .gitignore's, Git will ignore >> changes to those files. > > I misspoke. More accurately: > > If a file is *already* in the repository, then its name matching a > .gitignore pattern won't cause Git to ignore changes to it; Git > still will commit its changes easily. > > Only *new* files which match a .gitignore pattern will be ignored, > silently. > > If these particular new files have names (or extensions, or path > fragments, depending on the particular .gitignore pattern) similar > to files present in the repository, then this is confusing. > > Aug 23, 2015; 6:35am David Kastrup wrote: >> Basically, having files both in the repository and in .gitignore >> is a recipe for trouble. The patterns should likely be made more >> discriminatory. > > In order to make the relevant patterns more accurately > discriminatory, we might identify the programs (that we use) which > generate noise files (i.e., files we want to exclude from the > repository) of these kinds, and in which directories. Does anybody > know? > > Otherwise, we should try removing these particular .gitignore > patterns, and see whether our procedures still generate any of > these unwanted files—and in which directories. Then (obviously) we > can reinstate the patterns, and make them more discriminatory. > > Here's what Git blame says is the latest commit which changed the > relevant lines in /.gitignore: > > $ git blame .gitignore > > 915e0d52 (Jan Nieuwenhuizen 2006-12-05 14:54:32 +0100 2) > *-midi.ly 915e0d52 (Jan Nieuwenhuizen 2006-12-05 14:54:32 +0100 9) > *.eps 915e0d52 (Jan Nieuwenhuizen 2006-12-05 14:54:32 +0100 26) > *.svg >
Well I am not sure exactly what we're looking for but when I removed these entries in my .gitignore and then ran both an out of and in tree make doc, make test-baseline and a make check, I didn't get any files showing up when I then did a 'git status'. Is that good enough? James _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
