Holger have changed all C-Comments /* xxxx */ to C++Comments //
even in CONF-Files and even after #define and other preprocessor commands.
Bad to merge, with "Meld" merging is more or less possible.
My build directory is littered (by my own actions) with things like rocksndiamonds-sdl2 and rocksndiamonds.old.
Mine too!
Solution: Put all those files (file patterns) into the file ".git/info/exclude". (On my system, this is a symlink to "../../.gitignore.private", so I have the public and the private Git ignore file nicely next to each others.)
git status also whines about various graphics files created by the build.
Oops, right! I had these patterns in my private Git ignore file -- moved them to the public Git ignore file now!
Holger have changed all C-Comments /* xxxx */ to C++Comments //
even in CONF-Files and even after #define and other preprocessor commands.
Bad to merge, with "Meld" merging is more or less possible.
Not sure what this has to do with Git ignore files, but: If you simply use "git merge" instead of that other tool you used, it is in fact very easy to merge! I've just merged your changes to a copy of the latest "master" branch, and solving those few conflicts after the automatic merge took me less than five minutes.
You already have 'rocksndiamonds' and 'rocksndiamonds.exe' in .gitignore; it really seems sensible to just change that to 'rocksndiamonds*', anticipating (or in fact reacting to news) that files of that pattern are likely to accumulate there & are ignorable...
Ah, given .gitignore rules, I guess the entry ought to be '/rocksndiamonds*' (ignore them only in the root of the repository).