Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add switch to $patch_levels for Magento 2 Official Patches #136

Merged
merged 1 commit into from
Jul 17, 2017
Merged

Add switch to $patch_levels for Magento 2 Official Patches #136

merged 1 commit into from
Jul 17, 2017

Conversation

navarr
Copy link
Contributor

@navarr navarr commented Jun 7, 2017

Magento is a fairly popular software where composer-patches is especially useful. Patch files distributed by Magento in some special cases are based in the root directory, containing paths like a/vendor/magento/module-catalog. In cases such as these, if only a single module is referenced in the patch file then a -p4 flag will allow the patch to work as distributed by Magento.

Magento is a fairly popular software where composer-patches is especially useful.  Patch files distributed by Magento in some special cases are based in the root directory, containing paths like `a/vendor/magento/module-catalog`.  In cases such as these, if only a single module is referenced in the patch file then a -p4 flag will allow the patch to work as distributed by Magento.
@navarr
Copy link
Contributor Author

navarr commented Jun 7, 2017

Unnecessary if/when proposal in #76 happens

@cweagans
Copy link
Owner

Works for me. Thanks!

@navarr navarr deleted the patch-1 branch July 17, 2017 15:55
@hostep hostep mentioned this pull request Apr 13, 2023
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants