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

1.x backport: Allows patch-level to be specified per-project. #189

Merged
merged 1 commit into from May 11, 2018

Conversation

Projects
None yet
5 participants
@jhedstrom
Copy link

commented Jan 17, 2018

  • Backport to 1.x
  • Reroll of #101
  • Fixes #43
Allows patch-level to be specified per-project.
- Backport to `1.x`
- Reroll of #101
- Fixes #43
@bkosborne

This comment has been minimized.

Copy link

commented Feb 2, 2018

Would love to see this in! We're also having issues with applying Drupal core patches that introduce new files. They go to the wrong place.

@MPParsley

This comment has been minimized.

Copy link

commented Apr 11, 2018

Indeed, this should go in 1.x

@fenstrat

This comment has been minimized.

Copy link

commented May 10, 2018

This works a treat for core patches. Would also love to see this in 1.x.

@cweagans

This comment has been minimized.

Copy link
Owner

commented May 11, 2018

Despite what I said before, I'm okay with this. It's pretty low risk and solves some immediate problems for people using composer-patches. While I would really like to say that this is a 2.x feature, the reality is that 2.x isn't moving along as quickly as I'd like, and it's not fair to make people wait for something that doesn't have a realistic release date set.

Thanks for bringing this back up, and sorry I didn't give it more consideration before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.