-
Notifications
You must be signed in to change notification settings - Fork 2.7k
[release/3.1] backports dotnet#67763: fix build with musl 1.2.3 #28245
Conversation
@nekopsykose I see that you backported the musl 123 fix on Alpine's side. (thanks for that!) You removed whatever modifications in |
afaik those don't change any semantics (NULL == nullptr), it just failed to apply cleanly and i was lazy for a mere backport :) |
Gotcha, then for the upgrade to 3.1.418 I'll apply proper change - it's what upstream wants. |
0e94714
to
ff39f2f
Compare
Confirmed good build in Alpine pipelines |
@ayakael is this ready to merge? Can you get a sign-off from someone in your team? |
Ah, it's missing the |
@janvorli can you do a code review? Same as dotnet/runtime#67772 |
@ayakael, could you update the PR body with a template we use to get servicing approval? Once I get it from you, I will get an approval. Please refer an example from dotnet/runtime#68934 which includes:
|
@ayakael, I have a question to you. You put up servicing PRs for only .NET 3.1 and .NET 5. I don't see .NET 6 patch. What is your plan for .NET 6 patch? When fixing issues, we need to fix all the supported releases between the lowest needed (in this case .NET 3.1) and the currently supported release (.NET 6). |
@ayakael the PR has been inactive for a few months. I'll close it. Feel free to reopen if you can answer the questions above. |
Backports dotnet/runtime#67772 to release/3.1 to fix build with musl 1.2.3