-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Move SegmentWriteStream to shared resource #47180
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
Move SegmentWriteStream to shared resource #47180
Conversation
Thanks for your PR, @Skaanning. Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
Thanks @Skaanning! |
This looks good to me. Will do a sanity check to make sure the moved tests are still running. cc: @sebastienros |
Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Hi, sorry I don't quite know how the process works here. |
@Skaanning I didn't realize the PR was done by an external contributor, and hence you couldn't merge it once I approved it. |
Thanks @Skaanning! |
Move SegmentWriteStream to shared resource
Description
Moved SegmentWriteStream.cs from the projects
ResponseCaching
andOutputCaching
to the shared folder.Moved SegmentWriteStream namespace from
Microsoft.AspNetCore.ResponseCaching
andMicrosoft.AspNetCore.OutputCaching
toMicrosoft.AspNetCore.WriteStream
Fixes #45957