add MANIFEST which is GENERATED by distutils
Reasons for making this change:
if you use distutils.core to setup, the file MANIFEST is generated by distutils when run 'python setup.py sdist'
Some of these names relate to specific tools, others could be used by multiple tools. In particular, virtualenv, the most popular tool for creating Python environments, does not mandate any of these and venv/ or .venv are simply conventional. It is more readable to group all of these together.
For template rules (modern style) in Qt project file,
this file is autogenerated by qmake.
Example old style (pro file):
SOURCES += src/1.cpp \
src/2.cpp
Example new style, uses template rules (pro file):
SOURCES += src/*.cpp
qmake auto generate files with list of objects
object_script.*.Debug
object_script.*.Release
This file is autogenerated by qmake. It imports static plugin classes for
static plugins specified using QTPLUGIN and QT_PLUGIN_CLASS.<plugin> variables.
This file is autogenerated for static build
**Reasons for making this change:**
PuTTYgen is a widely used alternative to OpenSSH under Windows.
This rule allows private keys ignoring.
If this is a new template:
- **Link to application or project’s homepage**: https://www.chiark.greenend.org.uk/~sgtatham/putty/
The presentation software pdfpc [1] (which is handy for latex beamer slides) supports additional notes on the secondary screen provided by *.pdfpc files.
These can be autogenerated from latex documents with the pdfpcnotes package [2], thus should be ignored in a latex project (but not in others where they could have been created manually).
[1] https://pdfpc.github.io/
[2] https://github.com/cebe/pdfpc-latex-notes
[mkdocs](http://www.mkdocs.org/) is rising as an alternative to Sphinx for project's documentation. The default build command puts the generated documentation in a `site` directory at the root of the project which should be ignored.
From the Eclipse Documentation: "Make sure that the .project and .classpath files are under version control. These files must be stored in the repository so that other users checking out the projects for the first time will get the correct type of project and will get the correct Java build path." - http://wiki.eclipse.org/FAQ_How_do_I_set_up_a_Java_project_to_share_in_a_repository%3F
