Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Conversation

krwq
Copy link
Member

@krwq krwq commented Mar 30, 2018

2.1 squashed port of #28278
Seems like CI is hanging on master but we can still send a port PR

cc: @karelz @Tratcher

@stephentoub
Copy link
Member

Is this necessary if we're going to be doing a merge from master to 2.1 today or over the weekend anyway? These one-off ports can make that more difficult. cc: @weshaggard

@krwq
Copy link
Member Author

krwq commented Mar 30, 2018

@stephentoub I didn't realize there will be port happening, I thought it was already locked. If we are in fact doing it we can close this PR

@karelz
Copy link
Member

karelz commented Mar 30, 2018

The only reason would be to deliver the bits to ASP.NET faster - @Tratcher would it help you? If not, let's not complicate things ...

@karelz karelz added this to the 2.1.0 milestone Mar 30, 2018
@krwq
Copy link
Member Author

krwq commented Mar 30, 2018

I'm going to close this PR in this case

@krwq krwq closed this Mar 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants