Add comment to prevent *.sublime-project being ignored.

Adding wp-config.php Back Into Version Control

Based on advice in the documentation at
http://www.sublimetext.com/docs/2/projects.html

remove `npm-debug.log` entry

Ignore elf and hex files in C.gitignore

Dart.gitignore updated to reflect instructions provided by authors

Python.gitignore add coverage.xml

.classpath and .project files are *meant to be versioned*

Ignore Leiningen REPL history

Make Python .gitignore directory entries match only directories

This commit also alphabetizes the distribution/packaging section after
separating the directory entries from the file entries.  I left alone
a few entries that I'm not sure about (i.e. *.egg and the
"Mr Developer" section).

Reverting change to ignore build subdirectories

Conflicts:
	Objective-C.gitignore

tighter and more perl entries

Qt additions

Ignore Rails directories instead of their files

Added template for EPiServer

Fix having TYPO3 core-files as symlinks and fixed product-name

Ignore information for lein plugin directory. 

Magento 1.7 New Core Files & Folders Disregarded

added composer.phar to Symfony2 gitignore

Ignore generated MIDL header files

LaTeX.gitignore: add .brf for files generated by hyperref

.brf files are generated if the 'backref' or 'pagebackref' options of the hyperref package are enabled. These are intermediate files, so shouldn't be tracked.

Ignore *.loa in LaTeX; auxiliary 'list of algorithms' file generated by the algorithms package

Comment for .py[cod] files

Remove .project from Rails.gitignore since it is covered by Global/Eclipse.gitignore

Fixed SASS case (It's Sass, not SASS)

Create an ignore file for Vagrant's configuration and internal files.

From the documentation at http://docs.vagrantup.com/v2/getting-started/project_setup.html

"The Vagrantfile is meant to be committed to version control with your project, if you use version control. This way, every person working with that project can benefit from Vagrant without any upfront work."