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

Fix package name in docs

pull/1020/head
Jordi Boggiano 2012-08-21 16:04:11 +02:00
parent c446331a02
commit 036c81b1cc
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/05-repositories.md
View File

@ -68,7 +68,7 @@ The only required field is `packages`. The JSON structure is as follows:
{ {
"packages": { "packages": {
"vendor/packageName": { "vendor/package-name": {
"dev-master": { @composer.json }, "dev-master": { @composer.json },
"1.0.x-dev": { @composer.json }, "1.0.x-dev": { @composer.json },
"0.0.1": { @composer.json }, "0.0.1": { @composer.json },
@ -161,7 +161,7 @@ project to use the patched version. If the library is on GitHub (this is the
case most of the time), you can simply fork it there and push your changes to case most of the time), you can simply fork it there and push your changes to
your fork. After that you update the project's `composer.json`. All you have your fork. After that you update the project's `composer.json`. All you have
to do is add your fork as a repository and update the version constraint to to do is add your fork as a repository and update the version constraint to
point to your custom branch. For version constraint naming conventions see point to your custom branch. For version constraint naming conventions see
[Libraries](02-libraries.md) for more information. [Libraries](02-libraries.md) for more information.
Example assuming you patched monolog to fix a bug in the `bugfix` branch: Example assuming you patched monolog to fix a bug in the `bugfix` branch: