public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Editorial fix

pull/1303/head
Włodzimierz Gajda 2012-11-08 16:50:05 +01:00
parent 992249d4cc
commit c6ae3caf52
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/02-libraries.md
View File

@ -117,7 +117,7 @@ the `.gitignore`.
## Light-weight distribution packages
Including the tests and other useless information like .travis.yml in
Including the tests and other useless information like `.travis.yml` in
distributed packages is not a good idea.
The `.gitattributes` file is a git specific file like `.gitignore` also living

2
doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md
View File

@ -20,7 +20,7 @@ If you really feel like you must do this, you have two options:
- Limit yourself to installing tagged releases (no dev versions), so that you
only get zipped installs, and avoid problems with the git "submodules".
- Remove the .git directory of every dependency after the installation, then
- Remove the `.git` directory of every dependency after the installation, then
you can add them to your git repo. You can do that with `rm -rf vendor/**/.git`
but this means you will have to delete those dependencies from disk before
running composer update.