JackAidley

Thank you.

I was surprised to see that the default ignore.conf file generated excludes ignore.conf itself. I cannot understand why this would be desirable since it could result in different users have different ignore lists and thus files one user wants ignored being picked up by another user (and vice-versa). Is there a good reason for this behaviour I'm missing? And will removing ignore.conf from the ignore list so it is included in the repository cause any problems?

I had this too. The answer above is a... counter-intuitive way to understand both "major release number" and "just the first number of the current release".