Merge the django template into the python one since there is a significant overlap

Slashify Ruby files and directories.

arcresu pointed out that `*.gem`, `*.rbc`, `.rvmrc` might not be at
the top level in a repository. Thus, remove leading slashes for these.

Perhaps this is a little pedantic, but without the initial / all
such matches within the repository get ignored, and without the
trailing slash files as well as directories of that name get ignored.
e.g. Specifying `tmp` and `test/tmp` without slashes is redundant, as
`tmp` already ignores `test/tmp`, as well as every other `tmp` and
`tmp/`.

Added Bricx Command Center gitignore

Add Azure publish XML file

* Ignore Azure publish *.azurePubxml files
* Add a trailing slash to csx
* Remove random whitespace after build output

Conflicts:
	Yii.gitignore

Added nunit result and visual state

Ignoring "bld" directory

Prevent Unity .gitignore from ignoring non-Unity project files

Unity only generates project files in the top-level directory.
However, the current .gitignore will ignore all project files even
if they were not generated by Unity.

It is sometimes necessary to include non-Unity project files for
level editors or other utility projects that have been added to the
repository.

Unify approach to ruby environment normalisation

Added config files that should not be placed into repos by default as th...

Include crash.log file in nanoc.gitignore

Consolidate various IDE tempates into Global/JetBrains template

added NotepadPP.gitignore for Notepad++

Add "pip-delete-this-directory.txt"

Leiningen by default creates a 'target' directory, not 'targets'

Add Composer.gitignore for composer packages

Libraries/Projects using [Composer](http://getcomposer.org) for dependency management should include a `.gitignore` file like this.

It ignores the vendor folder which Composer uses for dependencies, classmaps and others. Composer keeps git repositories in this folder so it is cleaner if it is ignored.

[`composer.lock` should not be ignored.](http://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file)

> Commit your application's composer.lock (along with composer.json) into version control.

> For your library you may commit the composer.lock file if you want to. This can help your team to always test against the same dependency versions. However, this lock file will not have any effect on other projects that depend on it. It only has an effect on the main project.

Sort TeX template by packages (and rename)

Added Visual Studio .suo files