Florian Fida [Wed, 17 Jun 2015 19:46:54 +0000 (21:46 +0200)]
Update Typo3.gitignore for CMS v6.2
Typo3 now has an official way of overriding Configuration (AdditionalConfiguration.php).
/t3lib has moved into the /typo3 Directory.
Removed v4 specific ignores because it is deprecated and should no longer be used.
There were ignores missing for the symlinked setup.
Carl Suster [Sat, 30 May 2015 04:07:11 +0000 (14:07 +1000)]
Merge pull request #1523 from dash00/master
[Tex] Change *.mtc0 to *.mtc[0-9] *.mtc[1-9][0-9]
>`\@tocfile`
The name of the file containing the minitoc is constructed from `\jobname` and a suffix `\@tocfile`, which is `.mtc` (long extensions) or `.M` (short extensions) followed by the absolute number of the minitoc.
Jeremy Coatelen [Fri, 15 May 2015 12:21:22 +0000 (14:21 +0200)]
[Tex] Change *.mtc0 to *.mtc[1-9][0-9]
When using minitoc package, LateX often generates multiple .mtc files such as `*.mtc0`, `*.mtc1`, ..., `*.mtc13`, ... This patch allows one to ignore all *.mtc files from index 0 to index 99 (ignoring `*.mtc[1-9][0-9]`).
Zander Bolgar [Thu, 14 May 2015 19:03:22 +0000 (15:03 -0400)]
Remove Meteor.gitignore
There are only two entries in this .gitignore, and both are not needed.
- .meteor/local is already ignored by the standard Meteor .gitignore that is included with every project. This is redundant and should b left solely to the standard Meteor .gitignore in case this changes in the future.
- .meteor/meteorite should no longer be in any Meteor project. Meteorite was a package manager for Meteor, but it has been replaced by an official package manager built into the Meteor CLI. This directory should not exist, except on out of date Meteor projects which already have this ignore present.
Darwin Bautista [Thu, 7 May 2015 05:39:08 +0000 (13:39 +0800)]
Android: Remove redundant pattern for matching build directories
build/ already matches all directories named 'build' in the repository,
regardless of level. Gradle can have more than two levels of project nesting.
However, /*/build/ matches only the 'build' directories of 2nd-level projects.
Thus, the first pattern is more appropriate than the second.
The file name was incorrect, so it was having no effect. Also, the sandbox environment that this was supposed to be ignoring is deprecated. Probably best to just drop it entirely.
Adding a few more files/file extensions/directories for Synopsys VCS.
This new version adds:
- fsdb waveforms
- simv.db.dir/ directory for VHDL top configs
- ucli.key
- vc_hdrs.h
- Also added a few comments about where each one of the files come from.
Made it so the folders only get ingored in the root
With the current setup these folders are ignored in the whole repo, but they're only automatically generated in the project root so it makes sense to only ignore the ones in the root.
I made this change because one of the assets in my project uses a folder called 'Library', and I was wondering why it never uploaded that folder.
This change was introduced in 3bb4e51184066f5cf60daa029c31e7f52398353b, where it was marked as changed due to a typo. However, that is the correct name of this particular virtual environment. See https://hackage.haskell.org/package/virthualenv
Ignore timing.properties from takari-smart-builder
This extension is an alternative scheduler to build multi-module Maven projects.
It stores and updates timing for every build run in .mvn/timing.properties.
riosc [Wed, 11 Mar 2015 18:53:11 +0000 (15:53 -0300)]
removing aditional white space
removing this aditional white space avoid a mistake for beginners developers ignore the pod directory, because is confusing to note when they remove the '#' character and git still is tracking the pod dir.
jake johns [Tue, 10 Mar 2015 07:49:24 +0000 (02:49 -0500)]
Add ".env" to Laravel.gitignore
Laravel 5 uses vlucas/phpdotenv for env configuration.
http://laravel.com/docs/5.0/configuration#environment-configuration
Previous version used env.php files. the new configuration files do not have
.php extension
(cdep)illabout [Tue, 24 Feb 2015 07:10:30 +0000 (16:10 +0900)]
Remove cabal.config from Haskell.
The Stackage project provides a cabal.config which locks in a specific
package set. This file should be shared between developers project so
that everyone is developing using the same versions of packages.