- Add developer notes about
.gitignore. - Remove qt creator specific files from gitignore, to be consistent
Context: discussion in #6813, this is a bit of a FAQ so worth mentioning.
Good.
You should mention the simple command line however which does most of the hard work as per https://help.github.com/articles/ignoring-files/#create-a-global-gitignore
Thanks for the information, very helpful!
ACK
ACK.
- Add developer notes about `.gitignore.`
- Remove qt creator specific files from gitignore, to be consistent.
You should mention the simple command line however which does most of the hard work as per https://help.github.com/articles/ignoring-files/#create-a-global-gitignore
Added a mention of that - personally I prefer editing the config file manually, instead of memorizing the command, don't think it's very hard work :)
170 | @@ -171,3 +171,36 @@ Threads 171 | - BitcoinMiner : Generates bitcoins (if wallet is enabled). 172 | 173 | - Shutdown : Does an orderly shutdown of everything. 174 | + 175 | +Ignoring IDE/editor files 176 | +-------------------------- 177 | + 178 | +In closed-source environments in which everyone uses the same IDE it is common 179 | +to add temporary files it produces to the project-wide `.gitignore` file.
Also fairly standard practice in open-source environments... (Not saying we have to do it, but this description isn't correct.)
In my experience in - much more heterogeneous, multiplatform - open source projects it's rare to see ignores for specific tools that some of the developers use
I think the point is that ignore files should always be specific to the project, and not to the developer's environment. So IDE files for example should always be in the user's own gitignore and not the project source's.
I'm thinking things like *~
ACK
ACK .gitignore diff
Meh, "doesn't hurt" on the dev notes.