Skip to content

Porting #9528 to release 2.0 branch #9972

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

Merged
merged 3 commits into from
Jul 29, 2016
Merged

Conversation

riknoll
Copy link
Member

@riknoll riknoll commented Jul 26, 2016

Porting #9528 to release 2.0 branch

I squashed the commits from that branch to a single commit and cherry-picked the results to make this PR cleaner, but the original PR included several commits

@weswigham
Copy link
Member

weswigham commented Jul 26, 2016

This needs to include commit 8cbbcd0 as well, or we'll ship the RegExp DoS we encountered with the next 2.0 release.

@riknoll
Copy link
Member Author

riknoll commented Jul 26, 2016

@weswigham Thanks, cherry picked the commit.

@riknoll
Copy link
Member Author

riknoll commented Jul 27, 2016

@weswigham am I good to merge this?

@weswigham
Copy link
Member

Probably? But I'm not a formal gakekeeper of the 2.0 branch - cc: @RyanCavanaugh

@riknoll riknoll merged commit d98846b into release-2.0 Jul 29, 2016
@riknoll riknoll deleted the explicitly_included_globs_2.0 branch November 1, 2016 00:29
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants